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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context: the saved-quotes exclusion (blast radius) and the authentication requirement, including that an unauthenticated call triggers a sign-in prompt on printdash.io.

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 action and target, then scope exclusion, then the auth prerequisite. 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?

With an output schema present and only one parameter, the description covers the destructive scope and auth prerequisite well. The remaining gap is line_id provenance and error behavior on an unknown id, which matters for a destructive call.

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 0%, so the description carries the burden for the single parameter. It identifies line_id as the line identifier but does not say how to obtain it (e.g., from get_cart) or what happens with a stale/invalid id, so compensation is only partial.

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 and resource with scope ('Removes one line from the cart by its line_id'), which distinguishes it from clear_cart (all lines) and update_cart_line (modify rather than remove). The 'Saved quotes are not affected' clause further bounds it.

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 implied by 'removes one line' versus clear_cart, and the saved-quote exclusion gives a negative boundary. But it never explicitly names when to pick this over update_cart_line or clear_cart, leaving the agent to infer.

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