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

Annotations declare readOnlyHint=true, but the description describes burning LP tokens, requires an atomic LP approval, and mentions cleanup — all hallmarks of a state-changing transaction. This is a direct contradiction an agent could act on incorrectly. Flagged as an annotation contradiction.

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?

Six short clauses, front-loaded with the core action, with no filler. The telegraphic style is dense but each clause adds a distinct fact (router, fees, minima, derivation, unwrapping, approval/cleanup).

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?

An output schema exists, so return values need not be explained, and the derivation of the LP address plus the approval requirement are useful inclusions. Still, for a 9-parameter transactional tool the description omits deadline behavior and chain coverage, and its most consequential gap — the mismatch with the readOnly annotation — leaves the agent without a reliable safety picture.

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 78%, so the schema carries most parameter documentation. The description adds real meaning for a few fields — minima are raw values protecting proceeds, the LP token address is derived from the factory rather than supplied, and unwrap_native is optional — but says nothing about deadline, sender, or chain_id semantics. Baseline 3 is appropriate.

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 (burn) and resource (an exact LP amount) via the canonical V2 router, plus the scope detail that accrued fees are realized with principal. It also distinguishes the V2 flow from V3/V4 siblings by noting 'V2 has no separate fee claim,' which no other sibling covers. It stops short of naming the V3/V4 remove-liquidity siblings explicitly.

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 (withdraw liquidity from a V2 pool) and the prerequisite 'Requires atomic LP approval and cleanup' gives an actionable precondition. However, there is no explicit when-to-use versus prepare_uniswap_v3_remove_liquidity, prepare_uniswap_v4_remove_liquidity, or prepare_lp_position_withdraw, and no when-not guidance.

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