remove_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the destructive nature of the operation and clarifies two non-obvious behaviors: the BRING_LIST default when list is omitted, and oldest-match removal when item_uuid is not given. It does not document failure modes or idempotency, but the essential behavioral traits are clearly disclosed.

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 compact and front-loaded: one purpose sentence followed by a concise three-line Args block with no filler. Every sentence earns its place by contributing information needed to call the tool correctly.

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 definition is complete for an agent to invoke correctly: all parameters are explained, the default-list behavior and duplicate-handling policy are stated, and an output schema exists so return-value documentation is unnecessary. The sibling tool names cover the remaining edge case of marking an item as purchased.

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 0%, but the Args section fully compensates by explaining each parameter with examples and relationships (e.g., item_uuid sourced from get_list_items, and the behavior when it is omitted). This adds significant meaning beyond the bare schema titles.

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 opening sentence gives a specific verb and resource ('Delete an item from a shopping list') and adds the crucial distinction 'without marking it as purchased', which clearly differentiates it from the sibling complete_item. This is unambiguous and action-oriented.

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?

The description implies when to use this tool by contrasting deletion with marking purchased, but it does not explicitly name complete_item as the alternative. It does provide clear guidance on optional parameters (omit list to use the BRING_LIST default, supply item_uuid to disambiguate duplicates), helping an agent decide how to invoke it correctly.

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