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

Beyond the annotations (which already declare read-only/idempotent/open-world), the description discloses cost and quota behavior ($0.002 per call, 10 free/day, then an x402 payment-required result), and error semantics (isError with a message on invalid input or upstream failure, and that failures are not charged). These are operational traits an agent cannot obtain from the annotations or schema.

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 what the tool returns, then usage, then pricing, then error behavior — a sensible priority order with no filler sentences. It is a dense single paragraph, but every clause carries information.

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 explanation is unnecessary, and the description still covers scope, sibling routing, pricing/quota, and error handling for a one-parameter tool. Nothing an agent needs to call this correctly is missing.

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% and the single 'pool' parameter is fully documented in the schema (base58 Solana address, 32-44 chars) plus a regex pattern. The description adds no format or syntax detail beyond that, so the schema does the heavy lifting — baseline 3 is correct.

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 resource (Meteora DLMM pool state) and enumerates exactly which state fields are returned (price, bin step, fees, TVL, volume, fee yield, APR/APY), so an agent knows precisely what it gets. It also explicitly separates itself from the sibling dlmm_positions by scope (one pool vs a wallet's positions).

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 target audience ('For LP agents choosing where to provide liquidity') plus a when-to-use rule: 'For one pool's state; for a wallet's positions use dlmm_positions.' The alternative tool and the condition selecting it are named directly, 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.