Orders: list

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

The description explicitly states 'Read-only, changes nothing', which matches the annotations (readOnlyHint=true, destructiveHint=false). It adds value by disclosing the seller restriction and the presence of a 'hasMore' flag in the response, extending beyond what annotations provide. No contradictions.

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 four sentences long, well-structured, and front-loaded with the main purpose. Every sentence provides useful information: purpose, read-only nature, usage advice, availability, and response feature. No unnecessary words.

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?

Despite having no output schema, the description explains that the response includes a list of orders, available actions for subsequent writes, and a hasMore flag for pagination. This covers the essential context for a read-only listing tool, though a bit more detail on the order structure would be ideal.

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 has 5 parameters with full descriptions (100% coverage). The description briefly mentions filters by ID, status, and creation date, which corresponds to the key parameters, but does not add substantial new meaning beyond the schema. Baseline 3 is appropriate.

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 it returns a list of delivery orders with filters, using a specific verb 'Returns' and resource 'delivery orders'. It distinguishes this tool from its siblings, which mostly deal with other domains like autoload or CPA, and from other order tools that perform mutations (e.g., 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 provides context on when to use this tool: as a starting point for subsequent write operations, and it mentions that it's available only to B2C sellers. It implies read-only use but does not explicitly list alternatives or exclusions. The guidance is clear enough for an agent to understand its role.

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