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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds useful payload context (what fields each order carries, totals in cents) and the backing endpoint, but says nothing about defaults, page-size limits, or the ordering of results. Adequate but not rich behavioral disclosure.

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?

Three tight sentences: purpose and paging first, then the return payload, then the sibling routing. Every sentence carries information and nothing is repeated from structured fields.

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 enumerating the order fields (number, status flags, totals in cents, workflow status, technicians), which is genuinely helpful. The only gap is pagination defaults (no stated default limit or ordering), which matters for a paged 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 coverage is 100% and both parameters are fully documented there, including their roles in paging. The description's 'paged' adds only a hint that skip/limit apply; it contributes no syntax, defaults, or max-limit guidance beyond the schema, so the baseline of 3 is correct.

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 work orders for the shop') plus a scoping qualifier ('paged'), and explicitly separates itself from shopmonkey_list_customer_orders. An agent can distinguish this from get_order or list_customer_orders without opening a schema.

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?

Names the alternative tool (shopmonkey_list_customer_orders) and the condition that selects it ('for one customer's orders'), which is exactly the decision point an agent faces between these two siblings. It also flags the paging pattern via skip/limit.

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