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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false. The description adds two things beyond that structured data: the required OAuth scope (cart:write) and the state effect ('Changes buyer or order state'), which is genuinely useful context for a mutation tool.

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, each earning its place: the purpose, the auth scope, and the state effect. The primary action is front-loaded before the operational details.

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?

Return values need not be described since an output schema exists, and the annotation set covers safety and idempotency. The description closes the remaining gaps (scope requirement, mutation effect) but says nothing about error behavior or whether removal is reversible, leaving a minor gap for a destructive operation.

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 coverage is 100%, and the schema field description already spells out the ownership constraint ('not product_id or another buyer's item'). The description only restates ownership at a high level, adding no syntax or sourcing detail beyond what the schema carries, so the baseline 3 applies.

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 ('Remove') and resource ('an item ... from their existing basket'), with the ownership scope ('owned by this buyer') distinguishing it from generic cart operations. It does not name sibling alternatives like update_cart_item or remove_favorite, so the agent must infer the boundary rather than being told 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?

The description implies when to use it (deleting a line item the buyer already has), and 'Changes buyer or order state' hints at the consequence. However, it gives no explicit exclusions or direction toward update_cart_item or remove_favorite, leaving usage contextual rather than stated.

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