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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that rows are grouped per shipment and exposes the underlying endpoint (GET /inventory_shipments/export), which hints at bulk export semantics, but it says nothing about result volume, rate limits, or what happens when status and time filters combine.

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?

Three dense sentences, front-loaded with what the tool returns before moving to filters and paging. No filler, though the telegraphic phrasing ('reference, SKU lines, announced quantity, quantity arrived and note') packs a lot into one clause.

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?

Eight optional parameters with no output schema, but the description compensates by naming the returned fields and how rows are grouped per shipment. Paging defaults and per_page bounds live in the schema, so nothing critical for a correct call is missing; the combination rules across filters remain unaddressed.

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 eight parameters are already documented, including the single-status constraint and free-text targets. The description restates the same facts (one status only, free text covering ZF number/tracking/type) and adds only the pointer that paging mirrors list_orders, so it delivers marginal value beyond the schema.

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 ('List inbound inventory shipments') and immediately clarifies the domain concept as 'goods you sent to the warehouse', plus enumerates the returned columns (reference, SKU lines, announced vs arrived quantity, note). It is clearly distinguishable from zenfulfillment_get_inventory_shipment by being a list, though it never names that sibling explicitly.

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?

Provides a constraint ('Filter by ONE status') and cross-references a sibling for paging behavior ('Paging as in list_orders'), which is genuinely useful. However, it never states when to use this versus get_inventory_shipment for a single shipment, nor any prerequisites or exclusions.

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