Remove a product from the trolley

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

Annotations already mark the tool destructive and idempotent; the description adds the signed-in session requirement and explains that a removal requires no pricing unit. This meaningfully supplements the structured metadata without 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?

Three short sentences, each adding distinct value: the operation and its effect, the pricing-unit exception, and the authentication prerequisite. Information is front-loaded and there is no 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 single-parameter mutation with annotations covering idempotence and destructiveness, the description covers the operation, its effect, authentication, and a special condition for invocation. It does not mention the response or error cases, but the absence of an output schema and the low complexity make this a minor gap.

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 documents sku with 100% coverage, so the baseline is 3. The description adds useful context by clarifying that the SKU identifies the line to remove and that no pricing unit is needed, which goes beyond the schema.

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 uses a specific verb and resource: 'Remove a line from the trolley entirely,' and clarifies the exact effect by comparing it to setting quantity to 0. This also distinguishes it from sibling tools like set_cart_quantity.

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 statement 'the same as setting its quantity to 0' plus 'No pricing unit is needed' gives clear context for when this tool is appropriate versus a quantity-setting alternative. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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