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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful cost/rate-limit context ('$0.002 per call (10 free/day)') and details the snapshot-like 'State' nature of the returned data. No contradiction with annotations exists.

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 compact sentences with no filler. The first sentence front-loads the most important content, the second provides usage context, and the third gives cost/free-tier information. Every sentence earns its place.

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 simple one-parameter read-only tool with no output schema, the description is complete: it enumerates all the major returned metrics, states the intended use case, and mentions cost/rate limits. An agent has enough information to select and invoke it correctly without additional documentation.

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 already described as 'DLMM pool (pair) address' with a validating regex. The description does not add new parameter-level semantics, but with full schema coverage there is no meaningful gap to compensate for.

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 states exactly what the tool provides ('State of a Meteora DLMM pool') and enumerates the specific data returned: price, bin step, fees, TVL, volume, fee yield, and APR/APY. It also signals the intended audience ('LP agents choosing where to provide liquidity'), which helps distinguish it from sibling tools like dlmm_positions or dlmm_whales.

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?

The phrase 'For LP agents choosing where to provide liquidity' gives a clear when-to-use context that differentiates this from position-tracking or whale-tracking tools. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of full exclusion guidance.

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