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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuine value beyond that with the sort order, the returned field set, the pagination contract (has_more/next_skip), and a PII warning that recipient names and addresses are real customer data. It omits auth/rate-limit behavior, keeping it short of a 5.

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?

Four dense sentences, front-loaded with purpose and sort order, followed by filters, paging, and the privacy note. Every sentence carries an agent-relevant fact and nothing is repeated from the schema verbatim.

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 no output schema, the description compensates by naming the returned fields and the has_more/next_skip envelope, which is the critical piece for correct iteration. Only auth/error behavior is left unaddressed, which is minor for a read-only list tool.

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 every parameter (top, skip, status, order_ids, created_from/to, merchant_references) is already documented with constraints and defaults. The description restates the paging and filter semantics at a high level without adding syntax or format details beyond the schema, 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?

Specific verb+resource ('List print orders of this Prodigi account') plus scope details: sort order, the fields included (status stage, items, shipments, charges), and the underlying endpoint. It is clearly distinguishable from the sibling prodigi_get_order, which fetches a single order.

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?

Explains the filtering contexts (status, creation time, order ids, merchant references) and the paging contract, which tells the agent when this tool is the right choice over single-order retrieval. It stops short of explicitly naming alternatives or exclusions.

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