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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still adds real value: the data source (V3 Swap event carrying active liquidity per trade), the observation window (~1 hour, travels with the answer), and an explicit limitation (no impermanent loss, no forecasting). It does not cover rate limits or failure modes for an invalid/pinned pool address, which keeps it short of a 5.

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?

The first sentence is well front-loaded, but the text runs long for a three-parameter tool and repeats itself: the 'picked a pool, now must pick a range' framing appears again after the sibling-routing sentence. The 'does not model and does not forecast / it replays' contrast is useful but phrased redundantly.

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 no output schema, the description still enumerates what comes back (per-width fees, fraction of window in range, count of walk-outs) and flags the missing impermanent-loss dimension against fee maximization. The ~1-hour replay window is disclosed so the agent can frame the answer's scope correctly.

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 description coverage is 100%, so all three parameters (address, quote, capitalUsd) are already documented with defaults and fallback behavior. The description adds only indirect meaning — that position size sets the share of active liquidity and therefore the fees — which the schema also states. Baseline 3 is correct when the schema does the heavy lifting.

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?

Opens with a specific verb and resource: replay real swaps to compare price range widths for a PancakeSwap V3 position, and names the two outputs (fees earned, time in range). It explicitly distinguishes itself from siblings pancakeswap_fee_tiers (tier selection) and pancakeswap_position_look (existing positions), so an agent can route without opening schemas.

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?

Gives an explicit sequencing rule ('use it after the pool is chosen, pancakeswap_fee_tiers picks the tier') and an explicit exclusion with the alternative ('for a position you already hold use pancakeswap_position_look'). The when-to-use condition is stated twice (pool picked, capital size known), leaving nothing to inference.

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