Albert Heijn: Delivery Slots

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 genuine value beyond that: Dutch time zone, the fact that this only shows availability (no booking side effects), and a sample return format ('15:00-17:00').

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?

Three tight sentences, each earning its place: purpose first, the booking constraint second, and return format last. No redundancy or filler.

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 low-complexity, single-optional-parameter read tool with an output schema covering return values and annotations covering safety, the description supplies everything an agent needs (what it lists, what it cannot do, and the shape of 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?

Schema description coverage is 100%, so the single 'days' parameter (including its default of 7) is already fully documented in the schema. The description adds only implicit time-zone framing ('per day', 'Dutch time') and no syntax beyond what the schema provides, so baseline 3 is correct.

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 (List) and resource (delivery time windows), plus scope (at the member's address, per day, Dutch time). No sibling tool covers delivery slots, and an agent can immediately tell this apart from cart/order/product tools.

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 clarifies that booking is NOT possible through this tool and only happens in the AH app or on ah.nl, which is a useful exclusion guiding correct invocation. It does not name alternative sibling tools, but none exist for this domain, so context is clear.

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