- Agentic AI
- Agent
- Intermediate
- ChatGPT
- Claude
- Gemini
- Published
Agent Tool Names, Descriptions and JSON Schemas from API Docs
Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.
You get: Working code with an explanation
Ready to use: no blanks to fill in.
The prompt
mkdir -p .agents/skills/agent-tool-names-descriptions-and-json-schemas-from-api-docs && curl -sL "https://prompts-gpt.com/prompts/agent-tool-names-descriptions-and-json-schemas-from-api-docs/raw" -o .agents/skills/agent-tool-names-descriptions-and-json-schemas-from-api-docs/SKILL.mdAct as a developer experience engineer who writes tool definitions for LLM agents. I will paste API docs or a function list below. If you don't know which format I need (OpenAI function calling, Anthropic tools, MCP or other) or what the agent's main goal is, ask me those two short questions before writing anything.
Rules:
- Use only endpoints, parameters and fields found in the docs. Never invent any. Put guesses under assumptions.
- Name tools as verb_noun in snake_case, distinct enough that two tools are never confused.
- Write each description for the model: what the tool does, what it returns and any side effects, in 2-3 sentences.
- Give each parameter a type, a description, an enum or format where the docs allow it, and mark required fields. Flag destructive or costly tools and suggest a confirmation parameter.
Output format, per tool: name, description, use when, do not use when (name the better tool), JSON input schema in a code block, one example call. Then add an overlap table of confusable tools, missing information in the docs, risks, and next actions.
Docs:
{paste your API docs or function list here}Example output
Tips and common edits
Use when wiring an API into an agent and the raw docs are too vague for reliable tool selection. Paste the docs or function signatures, then answer any format question before reviewing the schemas.
Questions about this prompt
More like this
More in Agentic AITool Permission Matrix and Function Spec for a Tool-Using Agent
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
20-Case Agent Eval Set with Pass/Fail Rubric for Normal, Edge and Unsafe Requests
Builds 20 test cases for your agent's task, with expected behavior, failure signals and a pass/fail rubric covering normal, edge and unsafe requests.
Agent Workflow Decomposition with Autonomy Levels and Stop Rules
Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.
Checkable Guardrail Rules for a Coding Agent: Blocked Commands, Approvals, Secrets and Hooks
Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.
Research Agent Brief: Source Discovery, Evidence Review, and Citation Table
Directs an AI agent to plan source discovery, grade evidence, build a citation table, and support a decision without claiming live browsing occurred.
Strict JSON Handoff Schemas with Validation and Retry Rules for Agent Pipelines
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Agent Run Pre-Mortem and Self-Correction Loop Designer
Designs verification checks, error handling, and a self-correction loop for an agent task before it runs, based on likely failure modes.
Design an AI Agent With Tools, Guardrails and Eval Cases Before You Build It
Turns an agent idea into a build-ready design: the job, the tools with their inputs and permissions, guardrails, failure handling and a set of evaluation cases to test it.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Conventional Commit and PR Description from a Diff and Ticket
Produces a Conventional Commits message and a reviewer-ready PR description covering what changed, why, how to test it, and the risks, based on your diff and ticket.
Failing Test First Bug Fix
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.