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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond what the annotations and schema supply — no note on default result window, freshness, or how include_diagnostics/include_raw_rows change the response. Adequate but thin for a list tool with a default limit and date filters.

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, zero waste: scope first, routing hint second. Nothing is repeated from the title or annotations, and the alternative is placed after the primary purpose.

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?

An output schema exists, so return values need no explanation, and the read-only safety profile is covered by annotations. The description covers scope and sibling routing but is silent on why 9 optional parameters matter (e.g., date filtering / pagination intended for large result sets), a minor gap for a tool with a default 20-row limit.

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 nine parameters (limit, offset, sort_by, sort_order, date range, status, raw rows, diagnostics) are documented in the schema itself. The description adds no formatting, default, or interaction semantics beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Get AWD shipment-level data') and enumerates what is returned — shipment IDs, statuses, timestamps. It explicitly distinguishes itself from the closest sibling, get_awd_shipment_items, so an agent can route correctly without opening either 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?

Names the alternative tool and the condition that selects it ('For per-SKU quantities within a shipment, use get_awd_shipment_items'), which is exactly the routing decision an agent faces between the two AWD shipment tools. It gives no exclusions against the broader AWD/inbound family (get_awd_inventory, get_inbound_shipments), so it stops short of full when/when-not coverage.

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