List store orders

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral detail beyond that: results are newest first, returned as summaries, and amounts are in the smallest currency unit. It does not mention pagination defaults or result limits, but covers the key behavioral traits.

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?

Three tight sentences with no filler. The main action and ordering are front-loaded, filters are summarized compactly, and the pointer to single-order retrieval earns its place by preventing misuse.

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?

For a read-only list tool with 100% schema coverage, the description covers ordering, summary granularity, currency units, filter categories, and the path to richer order details. Without an output schema, a bit more about pagination or response structure would help, but nothing essential is missing for invoking it correctly.

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 description coverage is 100%, so the schema already documents every parameter in detail. The description broadly mirrors the filter categories but adds no parameter-specific semantics beyond what the schema provides, meriting the baseline score.

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 uses a specific verb and resource: "List a store's orders newest first as summaries." It clearly distinguishes itself from order-detail retrieval by noting that full line items, addresses, and fulfilments require retrieving a single order.

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?

It gives clear context: this tool lists filtered order summaries, while a single order should be retrieved for detailed line items, addresses, and fulfilments. It does not explicitly name the sibling tool ecommerce_retrieveAnOrderV1, but the guidance is direct and actionable.

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