list_orders

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

With no annotations, the description carries the burden for behavioral disclosure. It mentions optional status filter and pagination, but does not state that this is a read-only operation, what the response structure will be, or any default ordering. The straightforward nature of a list operation mitigates this gap, but more context would be useful.

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?

The description is a single, concise sentence that leads with the primary action and scope, then the qualifying options. Every part earns its place, with no wasted words.

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 simple list tool with three well-documented optional parameters and no output schema, the description is mostly adequate. It clearly states the scope ('all orders for your store') and optional filters, but it does not mention the return format or any pagination details beyond the parameter names, leaving a slight gap in context.

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?

The input schema has 100% coverage with descriptions for page, limit, and status. The description adds little beyond the schema, only tersely summarizing 'optional status filter and pagination' which the schema already documents in detail.

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 uses the specific verb 'List' with the resource 'orders', and adds scope ('for your store') plus optional status filter and pagination. This clearly distinguishes it from the sibling tool 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?

The description implies when to use this tool: to retrieve all orders rather than a specific one, as contrasted with get_order. However, it does not explicitly mention exclusions or alternatives, so there is no direct 'use get_order instead' guidance.

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