list_discount_codes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'lists all discount codes,' which implies a read-only operation, but it does not mention pagination behavior (despite the 'first' parameter with a max of 50), response format, or any other side effects. Minimal behavioral context beyond the obvious.

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 a single, compact sentence with no filler words. It front-loads the core function and is appropriately sized for a simple list operation.

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?

There is no output schema and no annotations, so the description must convey return value expectations and behavioral nuances. It only says 'lists all discount codes,' omitting that the tool is paginated (with 'first' and max 50), that 'query' enables filtering, and what fields the list items contain. Under-specified for an agent to fully understand the tool's behavior.

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 input schema provides full descriptions for both parameters ('first' and 'query'), so the description adds no parameter-level information. Since schema coverage is 100%, a baseline score of 3 is appropriate even without additional parameter detail in the description.

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 states the verb 'Lists' and the resource 'all discount codes in the shop,' leaving no doubt about the tool's basic function. It does not explicitly distinguish from the sibling 'list_automatic_discounts', but the resource naming makes the distinction 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?

The description offers no guidance on when to use this tool versus alternatives such as 'list_automatic_discounts', nor does it mention any prerequisites, exclusions, or specific scenarios. It is a bare statement of function without context.

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