books_get_invoice_pdf

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

With no annotations, the description carries the full burden of behavioral disclosure but only states 'Get an invoice as PDF'. It does not reveal the return format (e.g., binary, URL, base64), authentication needs, error conditions, or whether it is a read-only operation.

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 that is front-loaded with the key action and resource. There is no unnecessary information; 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?

This is a simple tool with one parameter and no output schema, but the description is still incomplete. It does not describe what the returned PDF looks like (e.g., file path, binary, link), any prerequisites (e.g., invoice existence), or how errors are handled, leaving significant gaps for an agent.

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 schema has one required parameter, invoice_id, but the description does not mention it at all. With schema description coverage at 0%, the description should compensate, but it fails to explain what invoice_id is or how it relates to the PDF retrieval.

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 'Get an invoice as PDF' clearly states a specific action (get), a resource (invoice), and a format (PDF), distinguishing it from sibling tools like books_get_invoice that return invoice data rather than a PDF.

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 usage guidance is provided. The description does not mention when to choose this tool over alternatives such as books_get_invoice or books_get_invoices, nor any prerequisites like the invoice status.

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