Albert Heijn: Recipe

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

Annotations only declare readOnlyHint=true; the description adds the servings-scaling behavior, the shape of the returned data, and a post-retrieval linking convention for urls. No auth or rate-limit notes, but for a read-only lookup this is solid added context.

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 short sentences, each load-bearing: what is returned, how to scale it, and what to do next. The core purpose is front-loaded before the workflow advice.

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-value documentation is not required, yet the description still names the returned sections. Combined with the scaling note and the shopping workflow, an agent has everything needed to call it 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 description coverage is 100%, so both parameters are already documented, including that recipe_id comes from ah_search_recipes. The description's note on servings scaling restates the schema's own wording rather than adding new semantics, 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 (Get) and resource (Allerhande recipe by id) and enumerates the payload: ingredients, preparation steps, and nutrition per serving. It is clearly distinguishable from the sibling ah_search_recipes, which only finds ids.

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 context for two behaviors: set servings to scale quantities, and use ah_search_products plus ah_add_to_shopping_list to shop for the ingredients. It does not mention the more direct sibling ah_add_recipe_to_shopping_list, so the routing advice is helpful but not exhaustive.

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