get_invoice_pdf

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

The description adds no behavioral details beyond what annotations already provide. It does not disclose that the tool returns a PDF file, any authentication requirements, or the effect of the logopaper parameter. However, the annotations clearly mark this as a read-only, idempotent operation with no destructive side effects, so there is no contradiction.

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 only two words, which is too short to convey necessary information. This is under-specification rather than effective conciseness, as it omits critical context about the tool's purpose and behavior.

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 tool's purpose and the lack of an output schema, the description should explain that the tool returns a PDF for the specified invoice and mention the logopaper option. It provides none of this, so an agent cannot know what to expect from the tool call.

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?

Both parameters (invoice_id and logopaper) are fully described in the input schema with 100% coverage, so the schema carries the burden of parameter semantics. The description adds no additional meaning, but since the baseline is 3 for high schema coverage, this is acceptable.

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 'Show PDF' is extremely vague and does not specify that this tool retrieves the PDF for an invoice. It fails to distinguish from sibling tools like get_order_pdf or get_quote_pdf. The description essentially restates the tool's name in generic terms, offering no specific resource or action clarity.

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 guidance is provided on when to use this tool versus alternatives such as get_invoice_reminder_pdf or get_order_pdf. The description lacks any context about prerequisites, use cases, or exclusions, leaving the agent without direction on tool selection.

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