billing-generate_invoice_pdf

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

Description covers the basic action (generate and store) but no annotations exist. No details on whether the operation is destructive, permissions needed, file naming, or storage behavior beyond 'in the specified case'.

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?

Single sentence, 11 words, front-loaded with key action. Every part is necessary; no wasted 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?

For a simple generate-and-store tool with 2 parameters, the description covers the core purpose but leaves out details about output format acceptance, potential conflicts with existing files, and how the file item relates to other case operations. No output schema exists, so completeness is moderate.

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?

Schema coverage is 100% with descriptions for both parameters. Description does not add extra meaning beyond the schema; it simply mentions 'specified case' without elaborating on parameter usage.

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?

Clearly states the verb 'generates' and resource 'PDF invoice', and specifies it stores the result as a file item in a case. Differentiates from sibling tool billing-generate_invoice_tex by output format (PDF vs TeX).

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?

Implies usage for generating PDF invoices, but lacks explicit when-to-use guidance or alternatives. Sibling billing-generate_invoice_tex suggests an alternative, but no direct comparison or usage context is provided.

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