ecommerce_listDiscountsV1

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

With no annotations, the description carries the full burden. It discloses filter behavior and the data format for amounts (integers in smallest currency unit, whole-number percentages), but omits pagination details, rate limits, and explicit read-only confirmation. It adds some context but is not comprehensive.

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?

Two concise sentences, front-loaded with purpose and filters, followed by a useful data-format note. Every word earns its place; no redundancy.

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 tool, it covers filters and amount representation, but lacks pagination behavior and response structure. With no output schema, the description should offer more detail on what is returned (e.g., array shape, paging meta).

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%, so the schema already documents parameters. The description repeats the filter semantics (q, is_disabled) and adds no new meaning beyond what's in the schema. The amount format note pertains to response data, not parameter semantics.

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 explicitly states 'List a store's discounts', which is a specific verb+resource. It also details two filter dimensions (free text over code/name, disabled state), making it easy to distinguish from other ecommerce list tools like listProducts or listOrders.

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?

No guidance is provided on when to use this tool versus alternatives or when to avoid it. It does not mention any exclusions, typical use cases, or references to sibling listing tools.

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