Search Albert Heijn Stores

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds a genuinely non-obvious trait — results are cached for up to 24 hours, which tells the agent data may be stale. It does not say anything about result volume or failure modes for unresolvable queries.

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 short sentences, zero filler, with the core capability front-loaded and the caching caveat as a trailing qualifier. Nothing to cut.

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-only lookup with no output schema, this covers purpose, inputs, expected result content, and the cache staleness caveat. Only the shape of the returned store list is unstated, which is minor given there is no output schema to defer to.

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 with 100% schema description coverage, including its own examples ('Amsterdam', '1011NG'), so the schema already carries the semantics. The description's mention of postal code or city name duplicates that rather than extending it.

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?

Specific verb+resource: 'Search nearby Albert Heijn stores by postal code or city name', plus the three things the result answers (opening hours, distance, facilities). The word 'stores' cleanly separates it from siblings like ah_search_products and ah_search_recipes.

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 query form (postal code or city name) implies when to reach for it, but there is no explicit guidance on when not to use it and no named alternative — the store-vs-product-vs-recipe distinction is left to inference from the tool name.

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