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

Annotations already mark this as read-only and non-destructive, and the description adds valuable behavioral nuances: discount_percent is based on the store's own previous list price, large discounts may be one-off clearances, prices exclude shipping, and min_discount affects returned count but not total_on_sale. These details go well beyond the annotations.

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 front-loaded with the core action and then adds only high-value information: usage trigger, pricing caveat, and parameter details. No sentence is wasted or redundant with the schema/annotations.

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?

An output schema exists, so return-shape details are handled. The description covers all parameter semantics, usage context, pricing interpretation, and important caveats. An agent has everything needed to invoke this tool correctly.

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 0%, but the description fully compensates by documenting every parameter: country enumerates se/no/dk/fi, category lists valid values, min_discount gives an example and explains its filtering behavior, and limit specifies the 1-20 range. This gives the agent complete semantic information.

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 opens with a specific verb and resource: 'List beauty products currently discounted in a market, largest discount first.' It clearly defines the tool's scope and differentiates itself from price-history exploration by pointing to get_price_history.

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 explicitly states when to use the tool: 'Use when the user asks for current sales, offers or discounts, optionally within a category.' It also provides an alternative for related but different needs, noting that get_price_history shows the actual price trajectory.

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