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

The annotations already declare readOnly, idempotent, and non-destructive behavior, so the description does not need to restate safety. It adds minimal behavioral context by indicating that results are based on order amount, but it does not mention pagination behavior or output shape; the annotations cover the main side-effect concerns.

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 very short and front-loaded, but the 'Guidance' line exactly repeats the description, adding no new information. This mild redundancy prevents a higher score, though the overall length is appropriate.

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 simple list operation with no output schema and two well-documented pagination parameters, the description is mostly adequate. However, the lack of differentiation from sibling promocode list tools and the ambiguous 'based on order amount' filter leave some contextual gaps for an agent choosing among alternatives.

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 schema provides complete descriptions for both parameters (`page`, `per_page`), so the description adds little beyond the schema. The phrase 'based on order amount' hints at an implicit filter but is not connected to any parameter, leaving the exact filtering semantics unspecified.

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 identifies the action ('list') and resource ('promocodes'), and adds a specific qualifier ('based on order amount') that distinguishes it from sibling promocode-listing tools. However, it does not sharply contrast with alternatives like collections, product, or tags beyond the phrase 'order amount', which is somewhat implicit.

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?

There is no explicit guidance on when to use this tool versus sibling promocode-listing tools. The description implies an amount-related filter but does not explain scenarios, prerequisites, or how it differs from shop_list_promocodes_collections, shop_list_promocodes_product, or shop_list_promocodes_tags.

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