get_discounts

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Fetch discount codes' and doesn't disclose read-only nature, pagination behavior, or return format. For a simple read operation, some context is still lacking, but the minimal action is clear.

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, concise sentence with no wasted words. It is front-loaded with the action and resource, making it highly scannable. There is no redundancy or fluff.

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?

The schema fully documents the parameters, but the description lacks usage context, return value expectations, and alternative tool mention. For a straightforward fetch tool, it is minimally adequate, but the missing usage guidance and behavioral details make it incomplete for an agent unfamiliar with the domain.

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%, with clear parameter descriptions for 'after', 'first', 'query', and 'reverse'. The description adds no additional meaning beyond the schema, so baseline 3 applies. It doesn't clarify relationships between parameters or provide examples.

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 'Fetch discount codes from the store' clearly states a specific action (fetch) on a specific resource (discount codes). It distinguishes from sibling tools like 'get_discount_code' (singular) and 'create_discount' by indicating a plural list operation.

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 provides no guidance on when to use this tool versus alternatives such as 'get_discount_code' or 'create_discount'. It doesn't mention pagination, filtering, or any context for when this tool is appropriate, leaving the agent without strategic selection information.

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