remove

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the basic action ('remove from cart') but does not disclose important behaviors such as whether the operation is idempotent, what happens if the SKU is not found, or whether it removes all quantities or just one. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence: 'Remove from cart by SKU.' It has zero wasted words and clearly communicates the action and key parameter. It is appropriately concise for a tool with only one parameter.

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?

The tool is simple with one required parameter and no output schema or annotations. The description covers the core purpose adequately, but it misses some context that would improve completeness, such as whether the operation is destructive irreversibly or how it handles missing SKUs. Still, it is minimally viable for a basic cart removal action.

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 has a single parameter 'sku' with no description. The description mentions 'by SKU', which only restates the parameter name and confirms its role. It does not add meaningful details about the expected format, validation, or behavior with invalid input. Given the 0% schema description coverage, the description compensates minimally.

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 'Remove from cart by SKU' uses a specific verb 'remove' with a clear resource ('cart') and the key input method ('by SKU'). It clearly distinguishes from sibling tools like 'add' (the opposite action) and 'cart' (viewing the cart).

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 usage is implied by the straightforward action: use this when you want to remove an item from the cart by its SKU. However, there is no explicit guidance about when not to use this tool or any mention of alternatives, such as 'add' or 'cart_diff'.

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