list_orders

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

No annotations provided, so description carries full burden. Discloses auth requirement ('orders:read capability gate'), pagination defaults, and status filter. While it doesn't explicitly state read-only, the verb 'list' and auth gate imply it. Lacks detail on ordering or empty results.

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?

Concise and well-structured: one-line purpose, usage examples, args list, requirement. Could be slightly more compact by integrating use-when into purpose, but overall efficient.

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?

Covers auth, pagination, filtering. Does not mention that return is a list of orders (implied) or ordering. With output schema present, return details are not needed. Sibling tools are noted indirectly. Reasonably complete for a 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 has 0% description coverage, so description fully compensates. Explains limit (page size, default 25, max 100), offset (skip N), and status (optional filter with examples). Adds significant meaning beyond schema types and defaults.

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?

Clearly states 'List title orders for the authenticated organization' with a specific verb and resource. Differentiates from sibling tools like get_order (singular) and others.

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?

Provides concrete usage examples ('show me the last 10 orders', 'list orders awaiting closing'), giving clear context. Does not explicitly mention when not to use or contrast with get_order, but examples effectively guide the agent.

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