Add Items to Albert Heijn Shopping List

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds the meaningful context that this mutates the user's real Albert Heijn account. It does not explain idempotency, duplicate handling, or what happens on unknown free text, but the side-effect warning is genuinely additive.

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 operation stated first and the write warning second. Nothing redundant or padded.

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 mutation tool with no output schema and annotations already covering the safety profile, the description is nearly adequate. It omits return behavior, auth/prerequisite requirements, and duplicate/error handling, which would matter for a real-account write.

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 the items array and the text/product_id fields with examples. The description only restates the same union ('free-text items or products') without adding format, length, or batch-limit guidance, so baseline 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 (add) plus resource (shopping list), and clarifies the accepted input forms ('free-text items or products'), which cleanly separates it from ah_get_shopping_list and ah_remove_from_shopping_list. An agent can identify the operation without opening the schema.

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?

There is a clear implied context (adding groceries), and the 'WRITES to the real AH account' note signals this should be used deliberately rather than speculatively. However, no explicit when-to-use guidance or alternatives are given, e.g. whether a product_id from ah_search_products is preferred over free text.

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