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

Annotations already establish the safe read profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds genuine domain behavior on top: an open excursion on a cold-chain lane implies the load must be quarantined pending QA, and it instructs the agent to say so. That is actionable semantics the annotations cannot convey. It does not, however, describe response size, pagination, or what happens when the shipment_id is unknown.

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?

Front-loaded with the payload enumeration, then use cases, then the quarantine rule — a sensible order. The field list is dense and slightly overstuffed, but each item corresponds to real returned data, so almost every clause 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?

With no output schema and no annotation depth beyond safety hints, the description compensates by enumerating the return contents in detail and flagging the one decision-relevant derived state (an open excursion). For a single-parameter read tool, an agent has everything it needs to call it and interpret the result.

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 0% for the single required shipment_id, so the description carries the full burden of explaining the parameter, and it does not: it never states the ID format or where an agent obtains one (e.g. from list_shipments). 'One shipment' only weakly implies the parameter, adding no usable detail over the bare schema field.

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 names a specific retrieval verb-and-resource pair ('Everything Aeroz holds about one shipment') and then enumerates the exact payload: profile/thresholds, status, items, custody events with chip verification, telemetry assessment, ranked routes, and open findings. This is far more specific than the title or schema, and it clearly distinguishes the tool from siblings like list_shipments (plural) or trace_unit.

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 gives concrete trigger phrases ('where is it', 'is the cold chain intact', 'was it ever opened') that map directly onto the returned fields, so an agent knows when to reach for it. It stops short of naming alternatives such as list_shipments for enumeration or trace_unit for a single unit, so no explicit when-not guidance is offered.

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