Tool Description Writer for Function Calling
Write tool names, descriptions and parameters a model can use correctly.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
I am giving a model these tools: [TOOL_LIST_WITH_PURPOSE]. For each, the underlying function does [FUNCTION_BEHAVIOUR]. Common mistakes models make with them: [OBSERVED_ERRORS]. For each tool write a name in verb-noun form, a description of two to three sentences that says when to use it and when not to, and a parameter list with type, required or optional, allowed values and an example. Add a short note on what the tool returns, including error cases, so the model can recover. Check that no two tools overlap in purpose; if they do, propose a merge or sharper boundary. Return the definitions in JSON-schema style, then five example user requests with the tool you expect to be called and the arguments. Also point out any tool whose name or description invites the wrong use, suggest which tools should require confirmation before running, and note which parameter values should be validated by code rather than trusted from the model. Use this pattern for each description so the model can decide quickly. First sentence: what the tool does in plain words. Second sentence: when to use it, naming the user intent it matches. Third sentence: when not to use it, naming the nearest similar tool. For example, a tool that looks up an order says it retrieves the status of one order by order number, is used when the customer asks where their order is, and is not used to change or cancel an order. For parameters, list the format with a sample value and the rule for missing values, such as asking the user rather than guessing. Test every definition by asking someone who has not seen the tools to pick the right one for each sample request. Close with a regression list: sample requests that each tool must handle correctly, to re-run whenever a description changes.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.