Remove from cart

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried by structured data. The description adds the useful detail that removal can target either a line or the entire cart contents, but it omits precedence when both cart_id and all are supplied, whether the cart persists when emptied, and whether errors are returned for unknown cart_id.

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?

A single short sentence that front-loads the primary mode (one line) and then the secondary mode (empty cart). No filler, and the parameter names are used inline as anchors.

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 four-parameter destructive mutation with no output schema, the definition covers the two removal modes but not the result (does it return the remaining cart?), the module scoping, or the interaction between cart_id and all. Annotations cover safety, so the remaining gap is behavioral detail rather than risk disclosure.

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?

With 50% schema coverage the description contributes meaning for cart_id and all, but says nothing about module (mart vs bites), which is documented only in the schema, or how it interacts with removal scope. session_key is explained in the schema, so the description does not need to repeat it, but the relationship between cart_id and all remains undefined.

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 names a specific verb (remove) and resource (cart line / whole cart) and enumerates its two modes via the parameter names. It is clear enough to distinguish from foran_cart_view and foran_cart_add, though it never explicitly contrasts itself with foran_cart_update, which can also reduce quantities.

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 implied by the parenthetical parameter hints: pass cart_id to drop a single line, pass all=true to clear everything. There is no explicit guidance on when to prefer this over foran_cart_update (e.g. setting quantity to zero), and no preconditions such as requiring a valid session_key or an existing cart.

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