List discounts

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

Annotations already establish readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral detail about free-text/disabled filtering and the unit semantics for discount amounts, but it does not mention pagination behavior or response shape.

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 compact and front-loaded: the core purpose appears in the first sentence, followed by concise filter and value-semantics details. No filler or redundant restatement of the tool name/schema is present.

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 read-only list tool with fully documented parameters and safety annotations, the description covers purpose, filters, and value formats. It omits pagination details despite the page parameter, but overall it is adequately complete for an agent to invoke the 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 description coverage is 100%, so the schema already documents store_id, q, page, and is_disabled. The description largely restates the filter semantics for q and is_disabled, adding little beyond the schema; the amount-unit note concerns output values rather than parameters.

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?

Description opens with 'List a store's discounts,' which identifies a specific verb and resource. It is clear but does not explicitly distinguish itself from sibling list tools like ecommerce_listProductsV1 or ecommerce_listStoreOrdersV1, so it stops short of full differentiation.

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 conveys that this is the read-only listing operation for discounts and enumerates available filters, implying when it should be used. It does not provide explicit selection criteria, exclusions, or point to create/update alternatives such as ecommerce_createADiscountV1.

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