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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds useful behavioral context beyond that: deletion is permanent, irreversible, and removes all cart lines. It does not cover permissions or error behavior, but the critical destructive scope is made explicit.

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 short sentences, front-loaded with the irreversible effect and followed by the alternative. Every sentence earns its place with no redundant text.

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 destructive one-parameter tool with full schema coverage and annotations covering safety, the description is complete enough. It communicates scope, irreversibility, and the correct alternative tool; no output schema is present, so return values need not be described.

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 description coverage is 100%, so the cartId parameter is already fully documented, including UUID source and capability warning. The description adds no additional parameter semantics, which is acceptable given the high schema coverage baseline of 3.

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 states a specific verb and resource: 'Supprime DÉFINITIVEMENT un panier et toutes ses lignes.' It also distinguishes the tool from its sibling update_cart by naming the single-line alternative. An agent can immediately tell this is full-cart deletion, not line-level editing.

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?

It explicitly routes the agent to the correct sibling: 'Pour retirer une seule ligne, utilisez update_cart avec `remove`.' This gives a clear condition for using delete_cart (whole cart) versus update_cart (single line). No ambiguity remains.

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