Clear Basket

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

No annotations are provided, so the description carries the full behavioral burden. It never says whether clearing is reversible/undoable, what happens if the basket is empty, or whether this affects a shared or per-market basket — all essential for a destructive bulk mutation.

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?

One short, front-loaded sentence with no filler. It earns its place, though the trailing 'of a market' adds ambiguity rather than precision.

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?

An output schema exists so return values need not be described, but for a destructive bulk-clear operation with zero annotations and an undocumented optional parameter, the description leaves major gaps an agent needs to invoke it safely.

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 single 'market' parameter has 0% schema description coverage and defaults to null, but the description never explains what the parameter means or what the null default does (e.g. current/default market). The only hint is the vague phrase 'of a market'.

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?

Names a specific verb+resource: removing everything from the basket. The word 'everything' implicitly distinguishes it from remove_from_basket, though the sibling is never named and the awkward phrasing 'basket of a market' slightly muddies the object.

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?

No when-to-use guidance at all. With siblings like view_basket, remove_from_basket, and add_to_basket, the agent has to infer that clearing an entire basket is the destructive bulk alternative to removing single items.

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