Albert Heijn: Update Order Item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful context beyond annotations: the tool only works against an active delivery order, and setting quantity=0 removes the item, with ah_remove_from_cart as the explicit removal alternative.

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?

The core operation is front-loaded and every part of the description is relevant. The parenthetical precondition is a bit dense, and the quantity=0 removal detail is repeated in the schema, but the text remains efficient.

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 destructive cart mutation with no output schema and annotations covering safety, the description supplies the key missing context: order prerequisite, product_id sourcing, and removal behavior. Return behavior is not described, but that is a minor gap given the annotations and no output schema.

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 schema already documents both parameters and even states that quantity=0 removes the item. The description adds product_id provenance via ah_search_products or ah_get_cart, which is useful but limited beyond 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?

The description states a specific verb and resource: 'Set the quantity of a product in the active Albert Heijn delivery order.' It clearly distinguishes this cart-mutation tool from shopping-list tools by naming ah_add_to_shopping_list as the pre-order alternative.

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?

It gives explicit preconditions ('Requires an order'), explains how an order is started, names the relevant alternative for pre-order collection, and points to ah_search_products or ah_get_cart for product_id. It also names ah_remove_from_cart as an alternative for removal.

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