Get all orders

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: a concrete rate limit (100 req/10 s per shop) and confirmation that oversized page sizes are capped at 100. It omits any note on result ordering or what happens when filters match nothing.

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?

Two short sentences, front-loaded with the operational constraint an agent most needs (rate limit). Minor waste: the page-size cap is duplicated from the schema's size description rather than left to the schema.

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 read-only listing tool with annotations covering safety and no output schema, the definition covers pagination and rate limits but never describes the shape of a returned order or the default sort/order. Adequate but with a noticeable gap for an agent that must interpret results.

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 nine parameters are documented in the schema itself. The description only restates the page-size cap already present in the size parameter description, adding no new syntax, format, or filter-combination meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

"Returns all orders with pagination" states a specific verb (returns/list) and resource (orders), which is clear on its own. It does not, however, distinguish itself from the sibling single-order tools get_order and get_order_by_friendly_id, leaving the agent to infer that this is the bulk-listing variant.

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 on when to use this tool versus get_order, get_order_by_friendly_id, or any filtered search. The description never mentions that the optional email/status/date filters exist or when to reach for them, so the agent gets no routing help.

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