Add Jumbo Shopping List Items

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes further by disclosing that it WRITES to the real account and that an inactive list is activated as a side effect (with the opt-out flag). The explicit scope exclusion (basket, checkout, orders, payments) is valuable mutation 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 tight sentences, front-loaded with the action and scope, then side effects, then boundaries. Every sentence earns its place with no 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 3-parameter write tool with full schema coverage and no output schema, the description covers purpose, side effects, and boundaries well. It does not describe what the call returns (e.g. whether added/skipped items are reported), which is a minor gap.

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 items, dedupe, and ensure_active are already fully documented in the schema. The description echoes the example and activation behavior but adds no syntax or format detail beyond the schema, 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) and resource (Jumbo shopping list), with a concrete example (['eieren']). It is clearly distinguishable from siblings like jumbo_remove_shopping_list_items and jumbo_set_shopping_list_item_completed.

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?

Explains the ensure_active interaction and the scope boundary (never touches basket/checkout/orders/payments), giving clear context for invocation. It stops short of explicitly naming alternatives such as jumbo_search_products for finding exact product names.

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