Remove cart line

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

Annotations already disclose that this is a non-read-only, open-world, non-destructive operation. The description adds scope information—removing exactly one line, identified by lineKey or linkId—but does not explain reversibility, behavior when the line is missing, or side effects beyond the cart line itself.

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 with no waste; the core action and targeting method are front-loaded. The bilingual repetition does not obscure the primary instruction.

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 simple one-parameter cart mutation with full schema coverage and annotations, the description is largely complete enough to invoke correctly. Minor gaps remain around what happens if the lineKey is invalid or whether removal is reversible, but they are not critical for basic selection.

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%, and the single lineKey parameter is already documented in the schema, including the linkId alternative. The description restates the same targeting information without adding syntax, validation, or error details 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?

States a specific verb and resource: remove one cart line, and identifies how the line is targeted (lineKey or linkId). It distinguishes itself implicitly from cart_clear by saying "one line," though it does not explicitly name sibling tools.

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 tool's usage is implied by the operation: use it to remove a line from the cart. However, the description does not explicitly say when to use it instead of cart_clear or cart_set_quantity, nor does it state any prerequisites or exclusions.

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