Check off shopping item

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

Annotations already declare readOnlyHint=false, so the write nature is known; the description adds the specific effect of checking the item off. It doesn't add context like whether the item is removed, requires special permissions, or is reversible, but the schema documents dry_run and idempotency behavior. This is adequate but not rich.

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 with no filler, and the core action is front-loaded. The second sentence about needing item name/id is arguably redundant with the required schema field but is not harmful. Very economical.

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?

The tool is simple, has a complete output schema, and all parameters are documented in the schema. The main gap is the absence of usage guidance vs siblings, but that is captured in usage_guidelines. For a straightforward mutation, the description is largely sufficient.

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%; every parameter including item, member, dry_run, and idempotency_key is already described in the schema. The description only restates the item requirement, adding no new semantics beyond the schema. 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?

The description uses the specific verb phrase 'Checks an item off the shopping list,' naming both the action and the resource. This clearly distinguishes it from siblings like add_shopping_item, clear_shopping_list, and list_shopping. The additional 'Needs the item name or id' clarifies the primary input.

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?

No guidance is provided about when to choose this tool over alternatives. It doesn't mention that adding items should go to add_shopping_item or that listing should go to list_shopping, nor does it describe any prerequisites or context. An agent must infer usage from the name and purpose alone.

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