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

The annotations only declare readOnlyHint=true, and the description adds useful behavior: minima act as slippage protection for proceeds, burn is conditional on full emptying, and unwrap_native has a currency-verification prerequisite. However it never states that this only constructs an unsigned transaction for later signing or what permissions/approvals are needed, so an agent could read the described liquidity decrease, fee collection and NFT burn as immediate state changes despite readOnlyHint=true.

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 dense sentences, front-loaded with the core action, then protections, then optional-flag prerequisites. Little waste, though the 'Raw minima protect withdrawal proceeds' sentence is terse enough to be slightly cryptic without schema context.

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, return values need no explanation, and the description covers the action, the two optional flags and the safety minima across 11 parameters. The remaining gap is the prepare-versus-execute contract and deadline/approval expectations, which matter for a transaction-building tool flagged readOnly.

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 73% and most field descriptions are the bare word 'decimal integer'. The description compensates by clarifying that liquidity is an exact uint128 value, that amount0_min/amount1_min are raw minimums guarding proceeds, and by explaining the conditions behind the burn and unwrap_native booleans. It leaves sender, token0/token1, deadline and token_id meaning entirely to the schema.

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 uses specific verbs and resources: decrease uint128 liquidity, collect principal and accrued fees, optionally burn an emptied NFT. That is unambiguously a Uniswap V3 withdrawal preparation and is distinct from add-liquidity or pure fee-collection work. It stops short of explicitly naming the nearby siblings (prepare_uniswap_v3_collect_fees, prepare_uniswap_v4_remove_liquidity), so distinction relies partly on the tool name.

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 context is only implied through conditionals: burn applies only to a 'fully emptied NFT', and unwrap_native 'requires verified position currencies'. There is no explicit when-to-use or when-not-to-use statement, and no routing guidance versus collect-fees or the V4 remove-liquidity variant.

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