List Shopify Discounts

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description usefully adds what the response contains (codes, usage counts, discount values), but says nothing about pagination behavior despite exposing an 'after' cursor.

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?

Front-loaded purpose sentence followed by a tight bulleted example list; every line is doing work. Slightly longer than strictly necessary but no filler.

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?

With no output schema, the description correctly covers return contents, and the query examples cover the main filtering parameter. Pagination semantics remain undocumented, a minor but real gap for a list endpoint.

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 only 67%, with 'limit' carrying no description. The description compensates by showing real query syntax (status:ACTIVE, discount_type:percentage, title:SUMMER), which adds genuine meaning beyond the schema's minimal 'Filter e.g.' note; it does not, however, explain the pagination cursor.

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?

States a specific verb (List) and resource (discounts), and enumerates the sub-types it covers (code-based basic/free shipping/BXGY and automatic). It also names the return payload (codes, usage counts, values), so an agent knows exactly what class of object it is dealing with.

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 says the tool supports filtering via a query string and gives concrete query examples, which implies when to reach for it. However, it never states prerequisites, when not to use it, or routes to any alternative sibling, so usage is inferred rather than prescribed.

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