download_amazon_invoice

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

No annotations are provided, so the description must fully disclose behavioral traits. It does mention a verification step ('must match invoice-specific content'), which is useful, but it omits critical details: what happens on mismatch, error handling, file save behavior, permission requirements, or whether it is a read-only operation. This is insufficient for a tool with zero annotation support.

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?

Two sentences with no filler. The purpose and the key verification constraint are front-loaded, making it easy to scan. Every word contributes to the core meaning.

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?

With no output schema and no annotations, the description is incomplete. It lacks usage context (when to use, prerequisites), error behavior, and what the tool returns (success/failure indicators). An agent would be unsure how to interpret the result or handle mismatches, making this inadequate for reliable invocation.

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 all parameters are documented in the schema. The description adds only a vague link to order_id verification but no extra semantic value beyond the schema. Baseline 3 applies because the schema carries the 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 clearly states the action (Download), the resource (Amazon order invoice), and format (A4 PDF). It differentiates from siblings which are all get/export operations for data, not a PDF download.

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?

The description implies this tool is for obtaining invoice PDFs, but it does not explicitly state when to use it versus alternatives or mention prerequisites like authentication. The verification requirement hints at a precondition, but there is no explicit when/not guidance.

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