invoices_pdf

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond annotations: Pro plan requirement, base64-encoded return format with content type, and automatic/on-demand PDF generation timing.

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?

Three compact sentences, front-loaded with the core action and followed by important return and prerequisite details. Every sentence contributes useful information without repetition.

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?

The description covers the key facts an agent needs: what is returned, how it is encoded, the plan requirement, and generation behavior. It is slightly incomplete regarding error conditions or explicit alternatives, but no output schema exists and the return behavior is adequately explained.

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%, and both parameters (uuid and companyId) are already documented in the schema. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Download the PDF representation of an invoice.' This clearly distinguishes the tool from invoice data retrieval tools such as invoices_get and invoice XML export tools such as invoices_xml.

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?

It gives useful context by stating 'Requires Pro plan' and explaining when the PDF is generated. However, it does not explicitly say when to use this instead of siblings like invoices_get, invoices_export_zip, or invoices_share_links_create.

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