Read live pool state; plan a range and mint amounts from it

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

Explicitly declares read-only ('builds no tx') and mentions error conditions. With no annotations, this carries the full burden acceptably.

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-loaded with read-only indicator, each sentence adds value. Could be slightly more structured but efficient overall.

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?

Covers return fields, derived computations, and error condition. No output schema, but description hints sufficiently at what is returned.

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?

Explains rangePct, balance0, balance1, tickLower, tickUpper and how they interact to compute amounts. Schema has 0% coverage, so description compensates well.

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 clearly states it returns live pool state and lists specific fields (pool address, tick, etc.). It is distinct from sibling build tools which are transactional.

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 advises to recompute before build_mint, giving a clear use case. Does not specify when not to use, but the read-only nature is obvious.

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