remove_from_cart

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

With no annotations provided, the description carries the full burden. It discloses authentication requirements and the special meaning of quantity=0 for complete removal. It does not mention return format or error cases, but for a simple mutation, the key behavioral aspects are covered.

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 concise (three sentences), front-loaded with the core purpose, and every sentence contributes: usage condition, alternative tool, auth requirement, and parameter sourcing. No redundant or irrelevant text.

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?

Despite lacking an output schema and annotations, the description covers purpose, usage, auth, and parameter sourcing. It could have mentioned return behavior, but given the tool's simplicity and the availability of get_basket for checking results, the description is sufficiently complete for an agent to invoke it 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?

Schema coverage is 100%, so the baseline is 3. The description adds value by emphasizing the zero-quantity removal behavior and by directing the agent to source productId and price from specific basket-getting tools, which goes beyond the schema's field descriptions.

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 tool's action: 'DECREASE the quantity of a product in the basket or DELETE it entirely.' This is a specific verb and resource, and it explicitly contrasts with the sibling tool add_to_cart, making it easy to distinguish.

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?

Usage is explicitly conditioned on quantity change direction: 'Use this when the quantity is going DOWN.' It also names the alternative for increasing/adding: 'To ADD a new product or INCREASE quantity, use add_to_cart instead.' Additionally, it tells where to obtain required parameters: 'Get productId and price from get_basket or get_extended_basket.'

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