list_customer_orders

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds pagination behavior via the since_id cursor, which is non-obvious and valuable. It does not explicitly state read-only/no side-effects, but 'List' strongly implies it, and the pagination detail is the main behavioral nuance.

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, focused sentences convey purpose and pagination with no redundancy. Every word adds value, and the structure is clean.

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 covers the core purpose and pagination. It lacks an explicit note about choosing this over list_orders and does not describe the return shape, but that is partially mitigated by the schema and the straightforward nature of a list operation.

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 already describes all three parameters accurately, including the cursor behavior of since_id. The description adds no new parameter-level detail beyond what the schema provides, so the baseline score of 3 applies.

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?

Uses a specific verb ('List') and resource ('orders placed by a specific customer'), immediately distinguishing it from general tools like list_orders. The customer-specific scope is explicit and unambiguous.

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 clearly implies this is for retrieving orders for a specific customer, giving context for when to use it. However, it provides no explicit alternatives or when-not-to-use guidance, especially with sibling tools like list_orders and search_orders present.

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