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

Annotations already indicate destructive behavior, and the description adds valuable context by explaining this is a soft delete and that the item will no longer appear in list_shopping_list_items. This goes beyond the annotation by clarifying the observable effect while not contradicting it.

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 concise sentences with no fluff. The core action is front-loaded, the key distinction from buying is stated, and the consequence is clarified in the second sentence. Every word earns its place.

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?

This is a simple one-parameter tool, and the description covers the action, the distinction from similar operations, and the resulting behavior. The output schema exists, so return values are already structured. Nothing essential is missing for an agent to invoke this correctly.

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 fully documents the single id parameter at 100% coverage, including its source from add_shopping_list_item or list_shopping_list_items. The main description adds little parameter-specific meaning, but with full schema coverage, baseline 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 states a specific verb ('Remove'), the resource ('an item from the household's shopping list'), and explicitly distinguishes itself from marking an item as bought. It clearly differentiates from sibling tools like buy_shopping_list_item and list_shopping_list_items.

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 clarifies when to use it: when an item should be removed rather than marked as bought. It implies the alternative is buy_shopping_list_item and that this tool produces a soft delete. It does not explicitly enumerate all alternatives, but the contrast is clear and sufficient for this simple tool.

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