cart_clear

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

No annotations are provided, so the description carries full burden. It discloses scope (one shop vs. all) but not whether the operation is destructive or reversible, whether the cart object survives emptied or is deleted, or whether quantities/other cart state are reset — critical for a clearing operation.

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 efficient sentence with the scope information front-loaded; nothing is wasted. It is terse to the point that behavioral caveats are absent, but the structure itself is sound.

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 state-destroying tool with no annotations and no output schema, the description omits what happens to the cart afterward, reversibility, and what the call returns. The agent knows what it clears but not the consequences of calling it.

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 schema itself explains that the shop ID is optional and omitting it clears all carts. The description restates this only at a high level without adding format or edge-case detail, so baseline 3 is appropriate.

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 ('Clear') plus resource ('items from shopping cart') and scope ('for a specific shop or all shops'). It implicitly distinguishes bulk clearing from cart_remove_item by wording, but never names the sibling or explicitly contrasts them.

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 only implied: the optional shop parameter hints at narrow vs. global clearing, and the verb 'Clear' hints at bulk vs. single-item removal. There is no explicit when-to-use, when-not-to-use, or named alternative such as cart_remove_item or cart_view.

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