Albert Heijn: Remove from Shopping List

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation/removal risk is covered structurally. The description adds the two-mode removal model but says nothing about reversibility, behavior when an item is not on the list, or partial-failure handling, so it goes only modestly beyond the annotations.

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, front-loaded with the action and resource, then the mode-selection rule, then the discovery pointer. No filler or repetition.

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 no output schema and two fully described optional parameters, the description covers both invocation paths and where to obtain IDs, which is sufficient to call the tool correctly. It is slightly thin on outcome/error behavior for a destructive operation.

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% and the schema descriptions already explain 'use for product items' vs 'use for items without a product ID', so the description's guidance largely restates it. It does add the pointer to ah_get_shopping_list as the source of product_ids, which is minor value over the schema.

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 (Remove) plus resource (items in the Albert Heijn Boodschappenlijst) and explicitly scopes it to one-or-more items. This clearly separates it from ah_clear_shopping_list (remove all), ah_add_to_shopping_list, and the similarly named ah_remove_from_cart / ah_remove_from_favorite_list.

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 concrete routing rules: product items use product_ids, free-text items use names, and product_ids should come from ah_get_shopping_list. It does not, however, name the alternative for bulk removal (ah_clear_shopping_list), so the when-not case is left to inference.

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