Render branded invoice document

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

With no annotations provided, the description carries the full burden. It discloses the output format (HTML) and intent (print to PDF), but fails to mention whether the tool is read-only, requires specific permissions, modifies state, or handles errors. Important behavioral aspects like side effects or auth needs are omitted.

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 a single sentence of 20 words that conveys the core purpose and output format concisely. No redundant information or filler. It front-loads the key action and resource, earning its place efficiently.

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 simplicity of the tool (1 param, no output schema), the description should address prerequisites (invoice existence), error behavior, and output structure. It does not mention what happens if the invoice is missing, if rendering requires certain state, or how the HTML is returned. The agent lacks sufficient context for robust use.

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 single parameter 'invoiceId' has no description in the schema (0% coverage). The tool description does not explain what this parameter represents, expected format, or constraints. The parameter name is self-explanatory but the description should clarify it, e.g., 'The unique identifier of the invoice to render.' This omission forces the agent to guess.

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 verb 'Render', resource 'invoice', and output format 'self-contained HTML document ready to print to PDF'. While specific, it does not explicitly distinguish this tool from the sibling 'quote_render', which likely serves an analogous purpose for quotes. The purpose is strong but lacks sibling differentiation for a perfect score.

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 no guidance on when to use this tool versus alternatives (e.g., 'invoice_create', 'quote_render'). There is no mention of prerequisites, suitable contexts, or when not to use the tool. The agent is left to infer usage from the bare description.

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