remove_from_cart

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

With no annotations provided, the description carries the full burden. It reveals a critical behavioral trait: the tool is server-side only and requires a browser synchronization step. This goes beyond the schema, adding essential operational knowledge. It doesn't cover other side effects, but for a simple removal tool, this is significant disclosure.

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 sentences, front-loaded with the purpose, followed by a crucial caveat. No redundant words or filler. Every sentence earns its place, and the structure is ideal for quick comprehension.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is largely complete. It covers the main action, the server-side scope, and a critical synchronization edge case. It doesn't explain return values, but no output schema exists and the focus is on action, not results. Minor gaps remain but nothing critical.

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 description does not elaborate on the 'items' parameter or its structure. With schema description coverage at 0% per context signals, the description should compensate, but it doesn't mention where to find SKU or how the array should be formed. The schema does provide a description for 'sku', but the tool description adds no value beyond that.

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 clearly states the action ('Remove products'), the target ('Selver.ee cart'), and the method ('by SKU'). This is a specific verb+resource+method, and it distinguishes from sibling tools like add_to_cart, view_cart, and search_products.

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?

Provides explicit usage context: 'Server-side only' and a clear conditional instruction for when a browser is open (must also dispatch cart/removeItem via chrome-devtools-mcp). This tells the agent when and how to use the tool, though it doesn't explicitly contrast with alternatives. The instruction is practical and actionable.

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