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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds modestly useful context: results include tracking numbers, and it exposes the underlying GET /api/orders/shipments endpoint. It does not mention pagination behavior or auth needs, which is acceptable given the annotation coverage.

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 tight sentence plus the endpoint: the verb and scope are front-loaded and every clause earns its place. No filler or redundancy.

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?

For a low-complexity, zero-required-parameter list tool with 100% schema coverage and clear read-only annotations, the description covers scope, the two modes, included tracking numbers, and the endpoint. Without an output schema it could say slightly more about the return shape, but it is largely complete for the complexity level.

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 page, limit, status and since_created_date are fully documented in the schema; the baseline is 3. The description only restates the two status modes already captured by the enum, adding no syntax or format detail beyond the structured fields.

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 states a specific verb ('List orders') and a precise scope (label recently printed, or printed but not yet manifested), matching the two status enum values. This clearly distinguishes a 'printed' scope from related lists. However, it never names a sibling (e.g. list_shipped_orders, list_manifests) to route against, so differentiation is implicit rather than explicit.

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?

There is no guidance about when to choose this tool over the many sibling list tools (list_orders, list_shipped_orders, list_manifests, list_unshipped_orders). The description describes what the tool returns but gives no conditions, prerequisites, or exclusions for selection. Usage must be inferred entirely from the tool name.

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