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

Annotations already flag destructiveHint=true, but the description adds the details that matter: the item is removed entirely even if multiple recipes contributed it, and the call requires a Subscriber account. That subscription prerequisite and the breadth of the deletion are not derivable from the annotations or schema.

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 short sentences, front-loaded with the action and scope, then the alternative, then the consent constraint. Nothing is repeated from the schema and no sentence is 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 two-parameter destructive tool with full schema coverage and annotations, the definition covers everything an agent needs: what is deleted, how broadly, what tier is required, when to prefer the sibling, and that human consent is required.

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%, and item_id already points at get_grocery_list's items while session_token documents the header alternative. The description adds no parameter-level information, so the baseline 3 applies since the schema carries the burden.

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 and resource ("Remove one item from ... grocery list") and immediately scopes it ("whatever added it"), which is the exact distinction an agent needs versus the recipe-scoped sibling. The contrast with remove_recipe_from_grocery_list makes the tool identifiable 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?

Names the explicit alternative (remove_recipe_from_grocery_list) and the condition that selects it: take back only what one recipe added. It also states a consent gate — "Only do this when the human asked for it" — which is a when-not rule most definitions omit.

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