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

With readOnlyHint=true and openWorldHint=false, the safety profile is already covered by annotations, and the description adds genuine value by noting that fees are excluded and that outputs are rounded. However it says nothing about how slippage_bps affects the result, whether tick bounds must align to tick_spacing, or what happens on invalid ranges.

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?

Front-loads the verb and scope, then adds the short clarifiers 'Fees are excluded' and the state-acquisition pointer, each of which earns its place. The opening sentence is dense but not padded; no redundant restatement of the title.

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-value detail is not required, and the description covers input sourcing, mode selection, and fee exclusion for an 8-parameter read-only calculator. Remaining gaps are the semantics of tick_spacing/slippage_bps and any validity constraints on the tick range.

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?

At 50% schema coverage, half the parameters (tick_lower, tick_upper, tick_spacing, slippage_bps) have no schema text, so the description must compensate. It does partially: 'current sqrt-price snapshot' maps to sqrt_price_x96, 'raw token budgets' to amount0/amount1, 'exact liquidity amount' to liquidity, and 'explicit token bounds' hints at the tick pair — but tick_spacing and slippage_bps remain entirely unexplained.

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?

Uses a specific verb+resource ('Calculate V3/V4 range liquidity, rounded mint/burn amounts and explicit token bounds') and scopes it to concentrated-liquidity quoting rather than transaction building. It also names the sibling used to obtain inputs ('prepare_uniswap_reads'), though it never explicitly contrasts itself with the prepare_uniswap_v3/v4_add_liquidity siblings that would consume the quote.

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?

Explicitly states the prerequisite/data source ('Obtain current state using prepare_uniswap_reads') and two operating modes (raw token budgets vs. an exact liquidity amount). It lacks an explicit 'do not use for X, use Y instead' exclusion against the actual add/remove liquidity preparation tools.

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