Orders: list

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

The description confirms read-only behavior ('Read-only, changes nothing'), adds pagination info ('hasMore flag'), and mentions B2C seller restriction. This adds value beyond annotations (readOnlyHint, idempotentHint) without contradiction.

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?

Description is 4 sentences, front-loaded with purpose, and no wasted words. Every sentence provides essential context (purpose, usage, restrictions, output hint).

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 5 parameters and no output schema, the description covers purpose, filters, read-only, pagination, and usage guidance. It lacks details like default sorting or order of results, but is reasonably complete for a list 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?

Schema coverage is 100% with descriptions for all 5 parameters. The description summarizes filters (ID, status, creation date) but does not add new meaning beyond the schema. 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?

The description clearly states 'Returns a list of delivery orders' and lists filters (ID, status, creation date). It also distinguishes itself as a read-only starting point for subsequent write operations, differentiating it from sibling tools like orders_apply_transition.

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 says 'Use it as a starting point' and notes availability to B2C sellers. It implies when to use (for listing orders before mutations) but does not explicitly say when not to use or list alternatives beyond mentioning available actions.

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