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

The annotations already establish read-only, non-destructive, open-world behavior. The description adds meaningful runtime details beyond that: the returned manifest contents, the pre-signed PDF URL validity period, and the 422 retry condition.

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 compact and front-loaded: it states the returned artifact first, then the input source, then the retry condition and endpoint. Every sentence adds operational value.

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 one-parameter read tool with annotations and no output schema, the description supplies enough context to call it correctly: what it returns, where the id comes from, URL lifetime, and the retry behavior for 422. No important gap remains.

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 coverage is 100%, so the parameter is already well documented, including the distinction from the carrier's manifest number. The description still adds useful provenance by saying the manifest id comes from `shippit_book_orders` or `shippit_get_order`.

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 identifies the resource (booking manifest document) and the key input (manifest id). It distinguishes this from sibling tools by naming the tools that produce the manifest id, so an agent can route correctly without opening the schema.

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?

It states where the manifest id comes from (`shippit_book_orders` or `shippit_get_order`) and gives a concrete retry instruction for the 422 generating state. It does not explicitly state when not to use it or name a direct alternative, but the usage context is clear.

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