Remove From Basket

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

No annotations provided, so the description carries full burden. It says 'remove' implying mutation and irreversibility, but doesn't state whether removal is permanent, whether it requires confirmation, what happens to the basket total, or whether it fails if the line_id doesn't exist.

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 terse sentence with zero waste. The key identifier and its source are front-loaded.

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 destructive mutation tool with no annotations and 0% schema coverage, the description is too thin. It doesn't cover the undocumented 'market' parameter, failure modes, or the mutation's irreversibility, leaving an agent under-informed.

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%, so the description should compensate. It partially does by linking line_id to view_basket, but leaves 'market' (the optional parameter with anyOf string/null) completely undocumented in both schema and description.

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 (remove) and resource (basket line), and clarifies the identifier source (line_id from view_basket). Distinguishes adequately from siblings like add_to_basket, set_quantity, and clear_basket, though it doesn't explicitly contrast with clear_basket which also removes items.

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?

Only gives a hint about where the line_id comes from. No explicit when-to-use guidance, no mention of alternatives like clear_basket, add_to_basket to reverse, or set_quantity to modify instead of remove.

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