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

Annotations only declare readOnlyHint=true, so the description has room to add and does: initializing sqrt price implicitly creates the pool (a real side effect), use_native spends ETH and refunds excess, and exact approvals plus cleanup require an atomic wallet (i.e., this tool alone does not finish the job). What is missing is an explicit statement of what the call returns/produces and that no transaction is broadcast, which matters given the 'Mint' wording versus readOnlyHint.

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 two operating modes, then preconditions, then optional flags, then the wallet caveat. Dense and largely waste-free, though the telegraphic phrasing ("verify factory fee tick spacing") is ambiguous enough to cost a little clarity.

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?

For a 16-parameter, 13-required transaction-building tool with an output schema (so return shape need not be explained), the description covers modes, pool-creation side effect, native-ETH handling, and the approval/atomicity caveat. Gaps remain around tick alignment to tick_spacing, slippage/deadline semantics, and explicit non-broadcast behavior.

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 63% and most property descriptions are bare types ("address", "decimal integer"), so the description carries real weight: it clarifies token_id as the increase-existing-position path, amount0/amount1 as raw desired amounts with amount0_min/amount1_min as bounds, initialize_sqrt_price_x96 as pool creation, and use_native as native-ETH payment. It still leaves fee vs. tick_spacing relationship, deadline, and chain_id unaddressed.

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?

"Mint a ranged NFT or increase token_id" states a specific verb plus resource and covers both operating modes (new position vs. adding to an existing one) in the first clause. The v3 scope is implied by the name rather than stated, and no sibling (e.g., v2/v4 add-liquidity, prepare_lp_position_deposit) is named, so an agent must infer differentiation from 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?

"First verify factory fee tick spacing and position tokens/range" gives a precondition for use, and the initialize_sqrt_price_x96 / use_native clauses tell the agent when those switches matter. However, there is no explicit when-not guidance or pointer to adjacent tools (uniswap_v2/v4 add liquidity, quote_uniswap_liquidity, prepare_lp_position_deposit), so the routing decision is left implicit.

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