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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely non-obvious behavior: shipcloud returns no totals so next_page is a guess, and a full page suggests more results. That is exactly the kind of caveat an agent needs to page safely and avoid trusting a terminal empty page.

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 resource and return payload, then the paging caveat; nearly every clause carries information. The trailing 'GET /shipments' is low value for an agent and the paging sentences are slightly run-on, but there is no padding overall.

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 13 optional params and no output schema, the description compensates by enumerating returned fields and explaining the pagination heuristic, which covers the main risks of calling this tool. It stops short of clarifying ordering/filter interaction with page number (e.g. whether filters reset paging), which is the remaining gap.

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 85%, so most of the 13 parameters are self-documenting, and the baseline is 3. The description reinforces that filters are combinable and explains the page-chaining convention, but adds no syntax or interpretation beyond what the schema already states for each 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?

States a specific verb and resource (list shipments) and enumerates the payload an agent can expect (carrier, service, price, tracking number/URL, label URL, addresses, tracking events), which is more than the title gives. It does not explicitly distinguish itself from shipcloud_get_shipment or shipcloud_list_trackers, so sibling routing is left to inference.

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?

'Filters can be combined' and the paging instruction give operational context, and 'newest first as shipcloud returns them' sets ordering expectations. However, there is no statement of when to use this list versus shipcloud_get_shipment (single lookup) or shipcloud_list_trackers, and no mention of prerequisites. Usage is implied rather than routed.

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