Albert Heijn: Last-Chance Items

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

Annotations already declare readOnlyHint=true, and the description adds meaningful context beyond that: the dedicated bargainItems GraphQL endpoint and the 'today-only' time-scoped nature of the results. Auth/rate-limit behavior is not mentioned, but the safety profile is well covered.

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?

Purpose is front-loaded, followed by prerequisite and data-source details. The trailing instruction about linking product/recipe names to their urls is a useful output-handling note, though it is somewhat tangential to tool selection.

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 an output schema present, return-value explanation is unnecessary, and the description covers data source, time scoping, and prerequisites. It is nearly complete for a read-only lookup, missing only auth/rate-limit context.

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 100%, but the description adds value beyond it by clarifying the actual requirement (a store_id is needed) and the relationship between store_id and postal_code as primary vs. fallback inputs, information the schema leaves unstated with 0 required parameters.

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 and resource ('Get last-chance / vandaag-af / clearance items from an Albert Heijn store') with clear domain scoping. It implicitly distinguishes itself from ah_get_bonus_offers by emphasizing 'today-only markdown deals', but does not explicitly name sibling tools to sharpen the boundary.

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?

Gives explicit routing: requires store_id and directs the agent to ah_search_stores, or offers postal_code as an alternative when the store is unknown. This clearly names the helper tool and the fallback condition, though it does not contrast this tool against related offer/inventory tools.

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