remove_shopping_list_item

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

No annotations are provided, so the description must disclose behavioral traits. The description only says 'Remove an item' without mentioning whether the action is permanent, whether it can be undone, what happens if the item_id is invalid, or any side effects. This is a mutation tool, and the description lacks critical safety or reversibility information.

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?

The description is a single, clear sentence with no wasted words. It is appropriately sized for a tool with a single parameter and a simple action, achieving maximum conciseness without unnecessary 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 tool with one parameter, no output schema, and no annotations, the description is minimally adequate but lacks behavioral context. It covers the core action and parameter, but fails to disclose consequences of deletion, error handling, or any prerequisites. Given the simplicity, this is a borderline score.

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?

The schema already provides 100% coverage by describing item_id as 'The ID of the shopping list item to remove.' The description adds no additional meaning beyond that. Per the rubric, with high schema coverage, a baseline of 3 is appropriate.

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 clearly states the action (Remove) and the resource (an item from the shopping list). This distinguishes it from sibling tools like add_shopping_list_item and update_shopping_list_item, which perform different operations on the same list.

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 no guidance on when to use this tool versus alternatives. While the name and description imply the action, no context is provided about prerequisites (e.g., item must exist), when removal is appropriate, or when using update_shopping_list_item would be better instead.

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