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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the mutation and safety profile is covered. The description adds modest context by confirming this only flips a checked flag on the user's own list rather than mutating list contents, but it says nothing about error behavior for unknown ids or partial failures across a batch of up to 100 items.

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 sentences, zero waste, with the usage trigger front-loaded ahead of the behavioral statement. Nothing is repeated from the title or annotations.

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 two-parameter toggle with full annotation coverage and a complete schema, the definition is close to sufficient. The only missing piece is guidance on sourcing itemIds (the schema points to get_grocery_list) and what happens when some ids are invalid in a batch.

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%, including 'true to check off (bought), false to uncheck' and 'Grocery item id from get_grocery_list', so the baseline is 3. The description's 'bought (or still need)' phrasing reinforces the intent mapping but adds no format, limit, or provenance detail 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?

Description states a specific verb ('Marks') and resource ('items on the user's Recipe One grocery list') plus the two-state outcome (checked or unchecked). The action is distinguishable from siblings like add_to_grocery_list or remove_grocery_items, though it never names them explicitly.

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?

'Use this when the user says they bought (or still need) items' gives a concrete trigger condition tied to user intent, covering both directions of the toggle. It stops short of stating when not to use it or pointing to remove_grocery_items for deletion.

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