get_invoice_pdf

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the result is base64 encoded PDF. However, it does not explain the presence of cursor and per_page parameters, which are unusual for a single PDF retrieval, and does not disclose any rate limits or authentication needs.

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 concise sentence (10 words) that front-loads the key action and output. However, it omits useful information about the parameters and response structure, but remains efficient.

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 presence of cursor and per_page parameters (typically for pagination) and no output schema, the description should explain how these apply to fetching a single PDF and what the response structure looks like. The description is too sparse to fully inform an agent about usage.

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 description coverage is 100%, so the schema already documents all parameters. The description does not add any new meaning beyond what is in the schema, such as clarifying that 'id' refers to the invoice ID or explaining the purpose of cursor and per_page for PDF fetching.

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 'Get', the resource 'invoice PDF', and the output format 'base64 encoded version'. This is specific and distinguishes from sibling tools like get_invoice which returns invoice metadata.

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 vs alternatives, such as get_invoice or other invoice-related tools. The context is implied by the name and description, but no exclusions or comparisons are provided.

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