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. It only says 'list', implying a read operation, but omits details such as whether it is destructive, any rate limits, pagination behavior, or what happens if no orders exist.

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, which is concise, but it is too terse for the information needed. It lacks any structured presentation of key details like parameters or output, reducing its effectiveness.

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 absence of output schema, no parameter descriptions, and no annotations, the description is incomplete. It does not explain the return format, pagination, or any ordering behavior, which is insufficient for a list operation 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?

With 0% schema description coverage, the parameter 'limit' is completely undocumented in both schema and description. The description does not mention the parameter or explain how it controls the result size, leaving the agent with no semantic guidance.

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 'List recent Merchant orders' clearly states the action (list) and resource (orders). The term 'recent' adds scope, distinguishing it from 'get_order' which retrieves a single order. However, it does not explicitly differentiate from other list_* sibling tools beyond the resource name.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_order'. The sibling names imply that this tool is for listing orders as opposed to retrieving a specific one, but the description does not state this or provide any exclusions.

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