Get Commercial Invoice PDF

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

Annotations already indicate readOnlyHint and idempotentHint, so the description adds limited behavioral context. It notes the return of a PDF but does not disclose any additional traits such as authentication requirements or file size limits.

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 extremely concise with two sentences and a short args list. No unnecessary words, and the main purpose is front-loaded. 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?

Given the simple tool with one parameter and no output schema, the description adequately states what the tool does and what it returns. It could mention the file format or that the response is a binary PDF, but the phrase 'commercial invoice PDF' is sufficient.

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 parameter consignmentId is documented in the schema with the same description. The description adds no extra meaning beyond the schema, which already has 100% coverage. Baseline of 3 is appropriate.

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 tool returns the commercial invoice PDF for a consignment, using a specific verb and resource. This distinguishes it from other PDF retrieval tools like machship_get_dangerous_goods_pdf or machship_get_consignment_label_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?

The description mentions 'used for international shipments,' providing some context for when to use, but it does not explicitly differentiate from sibling PDF tools or state when not to use it. No alternatives are given.

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