orders_list_orders

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

With no annotations provided, the description carries the full burden. It mentions pagination and optional filtering, which are behavioral traits, but it does not explicitly state that the operation is read-only or describe the return format, sorting, or pagination cursor behavior beyond what the schema already provides.

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 sentence that is front-loaded with the core purpose ('List customer orders') and includes key modifiers ('filtered', 'pagination') without any waste. It is highly concise and well-structured.

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 list tool with four optional parameters and pagination, the description covers the primary functionality and filter/pagination capabilities. However, since there is no output schema, the description could provide more detail on the return format (e.g., that it returns a list of order objects with a next cursor).

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 the baseline is 3. The description mentions 'customer or status' filters and 'pagination', but these details are already present in the schema. It does not add new semantic meaning beyond the schema.

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 clearly states the tool lists customer orders with optional filters and pagination. The verb 'list' and resource 'customer orders' are specific, but it does not explicitly differentiate from the related sibling tool orders_search_orders.

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 usage for browsing orders with optional filters and pagination, but it does not provide explicit guidance on when to use this tool versus alternatives like orders_search_orders or orders_get_order.

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