Create an invoice

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description takes full responsibility for behavioral disclosure. It reveals that the tool returns a link, that invoice data travels in the URL fragment and never reaches a server, and that no signup or watermark is involved. This is highly transparent about privacy and output, though it omits error handling or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each adding distinct value: purpose, benefits, and data privacy. It is front-loaded with the core action and remains concise without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (14 parameters, nested objects, no output schema), the description covers the essential behavioral aspects and privacy model. However, it lacks specification of the return format (e.g., whether the response is a JSON object with a 'url' field), which would aid agent processing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3. The tool description does not add additional meaning beyond what the schema already describes for each parameter, so no extra credit is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a professional invoice'), the resource ('invoice'), and the output ('return a link that opens it'). It also distinguishes from the sibling 'list_templates' by specifying the purpose is to generate a new invoice, not list existing templates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (e.g., when the user wants to create an invoice and get a link). It mentions benefits like no signup and no watermark. However, it does not explicitly state when to avoid this tool or provide alternatives beyond the implied 'list_templates' sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.