Get Store Clearance Bargains (Overblijvers)

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine context beyond that: results are cached for up to 30 minutes, meaning data can be stale, and the markdowns are 'today-only' and dynamic. It stops short of describing the return payload or how discounts are represented.

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 tight sentences, zero padding. The scope-defining qualifier and the caching caveat each appear once and are front-loaded where an agent will read them.

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 single-parameter read tool with annotations and no output schema, the description covers scope, dependency (store ID from store search), and freshness. The only gap is that it never characterizes the response shape — presumably a product list with markdown prices — which would help the agent know what to do with results.

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?

Only one parameter, and schema description coverage is 100% — the schema already tells the agent it is a store ID number from ah_search_stores. The description adds nothing about the parameter beyond restating 'for a given store ID', so the baseline of 3 applies.

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 ('Fetch') and a precisely scoped resource ('today-only dynamic clearance markdowns (*vandaag-af* / 35% discount items) for a given store ID'). This clearly distinguishes it from broader siblings like ah_get_bonus_offers or ah_search_products, though no sibling is named explicitly.

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?

Usage is implied rather than stated: the schema's parameter description points to ah_search_stores as the source of store_id, establishing a workflow prerequisite. There is no explicit when-not guidance or comparison to alternative offer/markdown tools (e.g. ah_get_bonus_offers).

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