list_orders

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

No annotations are provided, so the description carries the full burden. 'List orders' implies read-only behavior, but the description does not explicitly state that this operation is non-destructive, nor does it mention pagination behavior or the default page size. The schema hints at these, but the description itself adds no behavioral context.

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 clauses deliver the core purpose and filters with zero filler. The key action is front-loaded and every word earns its place.

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?

Given the tool's simplicity, the description is mostly complete for selecting and invoking it. The schema covers all parameters including pagination defaults, and the description covers allowed statuses. A minor gap is that it does not explicitly say what happens when no filters are supplied or that results are paginated, but this is reasonably inferable from the schema.

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%, so the baseline is 3. The description adds value by enumerating the allowed status values ('pending, active, fraud, cancelled') and mapping 'client' to the userid parameter, which goes beyond the schema's generic 'Order status' and 'Only this client' descriptions.

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 states a specific verb and resource ('List orders') and adds the key filtering dimensions (status and client). The allowed statuses are even enumerated, making the tool's purpose unambiguous and distinguishing it from other list tools like list_invoices or list_clients.

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 gives no explicit when-to-use guidance or alternatives. It simply states what the tool does, leaving the agent to infer that this is the tool for listing orders based on the name alone.

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