download_invoice_pdf

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

Annotations already indicate the tool is read-only and non-destructive (readOnlyHint=true, destructiveHint=false). The description adds that it returns a PDF, which is consistent with annotations. No additional behavioral details (e.g., file format, size limits) are provided, but given annotation coverage, this is sufficient.

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, front-loaded sentence that conveys the core purpose without extraneous words. Every word earns its place.

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?

No output schema exists, and the tool returns a binary PDF. The description 'Gets pdf' implies binary output but lacks details on how the PDF is delivered (e.g., direct download, URL). Given the complexity (2 parameters, no nested objects), the description is adequate but could specify the return mechanism.

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 parameter coverage is 100%, with descriptions for 'invoice_id' and 'options'. The tool description does not add further meaning beyond the schema. Baseline of 3 is appropriate as schema carries the explanatory load.

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 'Gets pdf of specified invoice' clearly states the verb (downloads/gets) and the resource (invoice PDF). It distinguishes from sibling tools like 'download_delivery_note_pdf' and 'download_letter_pdf' by specifying the invoice context.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for retrieving a PDF, but does not mention when to choose it over other invoice-related tools (e.g., 'get_invoice' for data, 'send_invoice_by_email' for sending).

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