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

The description contradicts the annotations: it states the line is 'deleted from the cart' (a destructive action) while the annotations set destructiveHint=false. Per rubric, this contradiction forces a score of 1.

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?

The description is five focused sentences covering action, outcome, return value, alternative, and error handling. Each sentence adds necessary information with no filler.

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?

Despite the annotation contradiction, the description itself is thorough: it defines the operational effect, return payload, deterministic error codes, and the appropriate sibling alternative. This is sufficient for an agent to invoke the tool correctly, given the simple two-parameter schema.

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?

With 0% schema description coverage, the description compensates by clarifying that skuId identifies the line to be removed and that cartId is part of the return payload, implying its role as the cart identifier. However, cartId is not explicitly described, preventing a higher score.

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 opens with a specific verb+resource ('Remove a product line from a droplinked cart by skuId') and clearly distinguishes itself from the sibling tool cart.updateLineQuantity by noting that quantity changes should use that tool instead.

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 states when to use this tool (to fully remove a line) and when not to (to change quantity), naming the alternative cart.updateLineQuantity. This provides clear decision guidance for an agent.

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