list_shipments

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, covering the safety profile almost entirely. The description adds no behavioral context beyond that — nothing about pagination, what 'snapshots and events' returns, or ordering, which are relevant for a search tool.

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?

A single front-loaded sentence with no filler. It is efficiently sized, though arguably too sparse for a tool with five undocumented parameters.

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?

Given five parameters at 0% schema description coverage, no output schema, and rich but un-leveraged annotations, the description is far too thin. It omits parameter semantics, usage routing, and any return-shape hint, leaving meaningful gaps for correct invocation.

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% across five parameters (limit, query, offset, status, orderId), and the description supplies no meaning for any of them. With the schema silent and no compensating text, the agent cannot tell what 'status' filters on or how 'query' is matched.

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?

It gives a verb ('search') and a resource ('imported delivery snapshots and events'), but 'snapshots and events' is fuzzy and never clearly ties back to shipments, nor distinguishes it from siblings like list_orders or list_transactions. The purpose is implied rather than stated precisely.

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?

No when-to-use guidance, no prerequisites, and no mention of alternative tools such as list_orders or import_records. The agent must infer the use case entirely on its own.

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