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

With no annotations at all, the description carries the full burden, and it does contribute one genuinely valuable behavioral fact: unknown pools are not charged, which tells the agent the call is cost-safe to probe. It never states that the operation is read-only, says nothing about what is returned for an unknown/invalid pool beyond the pricing note, and gives no rate-limit or auth context.

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?

Two short sentences, front-loaded with the identity of the tool and the metrics, followed by the billing caveat. The metric list is dense but each item is meaningful; nothing is padded.

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?

There is no output schema and no annotations, so the description's metric enumeration usefully doubles as a return-value preview. Still missing for a metrics tool of this complexity: what happens on an unknown or non-Base address, how 'window' changes the figures, and what 'reference range' means. Adequate but with clear gaps.

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 coverage is 50%, so the baseline applies: 'window' is already documented in the schema as trailing days with an enum, while 'address' has only a regex pattern. The description adds real meaning by specifying the address is a Base concentrated-liquidity pool address, not a token or user. However, 'at a reference range' is unexplained and hints at a range input that does not exist in the schema, which may confuse the agent about how to control the reference range.

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 a specific resource and scope: a real-yield card for exactly one Base concentrated-liquidity pool address, and it enumerates the metrics returned (fee APR, LVR, net yield, fee-to-LVR ratio, volatility). This is enough to distinguish it from the plural sibling lp_real_yield_pools, though it never names that sibling explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (lp_real_yield_pools) for listing or comparing pools. The phrase 'for one ... pool address' only weakly implies the single-address use case; the second sentence is about billing, not usage selection.

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