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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description reinforces this while adding real context: the status is derived from the *current on-chain* pool price, the price orientation is B per 1 A, and it flags near-edge conditions. It does not state what happens on wallet/token mismatch or whether any state is fetched/cached.

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 core operation, then mechanism, then a behavioral note. Nothing is repeated from the schema or annotations beyond the brief 'Read-only' confirmation.

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 compute tool with no output schema, the description should ideally say what the result looks like (status field, threshold used for 'approaches an edge', distance-to-edge). It covers inputs and the core semantics but leaves the return shape and edge-proximity threshold undefined.

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 poolId, wallet, and positionMint are already documented with their defaults and constraints. The description adds no per-parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: computes live in-range/out-of-range status for a Raydium CLMM position against tickLower/tickUpper. That is concrete enough to distinguish it from performance/APR siblings, though no sibling is named to sharpen the boundary.

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?

Usage is implied by the computation described (checking whether a position is currently in range, and whether it is near an edge), but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_position_performance.

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