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

With no annotations at all, the description carries the full behavioral burden and does well: it discloses the paid model, the exact price ($0.005 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, the upstream data source (DefiLlama), and the endpoint URL. It stops short of describing response shape or any rate/limit behavior.

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?

It is short and front-loaded, leading with the paid flag and the core capability before cost, auth, and endpoint details. Every sentence carries information; the URL is slightly raw but is a legitimate access detail.

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 three-optional-parameter read tool with no output schema, it covers purpose, data source, cost, auth, failure policy, and the fields returned, which is most of what an agent needs. It omits pagination/limit behavior and any sense of response size, which would matter for a pools-across-chains result set.

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 sort, limit, and min_tvl_usd are already fully documented in the schema. The description adds no parameter-level meaning (no defaults restated, no guidance on choosing sort or TVL floors), which is the expected baseline when the schema does the work.

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 a specific verb and resource: live DeFi yields for the single protocol reservoir-protocol, listing exactly what is returned (pools across chains with APY, TVL, 7d APY change). It is unambiguous about scope, but it never names the sibling families it differs from (chain-level and token-level yield tools), so differentiation relies on the tool name.

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 only implied by the resource name: an agent can infer this is the tool for one protocol's pool yields. There is no explicit when-to-use/when-not, no pointer to the chain or token siblings as alternatives, and the pricing/auth sentences are commercial facts rather than selection guidance.

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