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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real context beyond them: saved quotes are untouched, a confirmation step is required for carts the customer did not fill, and authentication is mandatory with a concrete sign-in fallback on printdash.io. This is exactly the extra behavioral detail annotations cannot convey.

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?

Three tight sentences ordered by importance: action, scope exclusion, then safety and auth requirements. No sentence is redundant.

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 zero-param destructive mutation, the description covers action, side-effect boundary (quotes preserved), confirmation etiquette, and auth prerequisites, and an output schema exists to explain return values. Nothing material is missing.

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 tool takes zero parameters, so there is nothing for the schema or description to disambiguate; the baseline of 4 applies. The description correctly signals that the target cart comes from the ambient 'current buying context' rather than an argument.

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 precise verb and resource ('Removes every line from the cart') and scopes it to 'the current buying context', which implicitly separates it from remove_cart_line's single-line scope. An agent can tell exactly what this deletes.

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?

Gives a clear when-to-use condition plus an explicit caution ('Ask the customer before emptying a cart they did not just fill') and excludes saved quotes. It does not explicitly name remove_cart_line as the narrower alternative, so it falls just short of a 5.

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