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

With readOnlyHint=true, the safety profile is already covered; the description adds version-specific read constraints (V3 bounded owner-index enumeration, V4 known token IDs) and a verification checklist. It still omits auth needs, error behavior, and what 'bounded' means quantitatively.

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 front-loaded sentences, each carrying a distinct point: purpose, version behavior, and pre-liquidity verification. No filler or redundant restatement of the schema.

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 an 11-parameter tool with only 45% schema description coverage, the description covers the highest-risk version-dependent params but leaves v2, chain_id, hooks/pool_address distinctions, and the meaning of 'bounded' unexplained. Output schema and readOnly annotation reduce the burden, but the definition is not fully complete.

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?

The 45% schema description coverage leaves many parameters thinly documented, but the description adds real meaning for token_ids and owner_indices via the V3/V4 rules, and names fee, tick spacing, owner, and pool key as fields to verify. It does not explain chain_id, hooks, pool_address, or the v2 path, so compensation is partial.

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 names the resource ('wallet read bundles for pool state, reserves, positions and ownership') and the operation ('Return'), and distinguishes V3 vs V4 behavior. It does not name any sibling read tool it replaces or complements, so an agent still has to infer its routing versus get_uniswap_pool or get_positions_by_owner.

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?

It tells the agent to verify returned fields 'before preparing liquidity operations,' which supplies a preparatory-read context. However, it gives no explicit when-not-to-use guidance or alternatives such as the get_* read tools, and the version notes are constraints rather than routing rules.

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