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

Annotations already mark the operation as read-only and non-destructive. The description adds valuable context beyond annotations: the PDF link is short-lived, and the manifest contains specific data elements (shipment, order IDs, state). No contradiction with annotations.

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, front-loaded sentence with no redundant information. It immediately states the scope ('One manifest') and lists the key output components and the short-lived link, making it highly concise and structured.

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?

For a simple read-only tool with one parameter and an output schema, the description adequately covers the returned data (shipment, order IDs, state, PDF link). No additional information is necessary; the output schema handles structural details.

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 description for the single 'id' parameter is complete (100% coverage), stating it is the manifest id. The tool description adds no additional parameter semantics beyond confirming it returns one manifest. Baseline 3 applies when schema covers parameters.

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 retrieves a single manifest with shipment and order ID lists, state, and a short-lived PDF link. This distinguishes it from list_manifests and other get_* tools, and the title 'Get manifest detail' reinforces the specific purpose.

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 the tool should be used when needing details for a specific manifest (since it takes an id and returns one manifest), but it does not explicitly contrast with list_manifests or other alternatives. No exclusion criteria or explicit when-to-use guidance is provided.

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