remove_cart_item

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is structured. The description adds scope context (removes an entire line) but doesn't disclose what destruction means (whether the line can be recovered, affected totals, or auth needs). Adequate but not rich.

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 short sentences, front-loaded with the action and scope, followed by the sibling routing. Zero waste.

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-param destructive mutation with no output schema, the description covers the action, target, and alternative. Missing confirmation/irreversibility notes that a destructive tool ideally surfaces, but nothing essential to invoking it correctly is absent.

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% and both parameters carry only pattern constraints, so the schema under-delivers. The description partially compensates by naming cart_item_id as the target of removal, but leaves cart_id's role implicit and gives no format guidance. Baseline 3 given low coverage.

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?

Specific verb+resource (remove a cart line) with exact scope clarified ('one entire cart line by cart_item_id'). Explicitly distinguishes from the sibling update_cart_item, which handles quantity reduction. An agent can select correctly without opening a 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 alternative (update_cart_item) and the condition that selects it ('to reduce quantity'). Clear when-to-use-this-vs-that. Lacks explicit negatives (e.g., cannot remove partial quantity), but the contrast sentence carries most of the routing.

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