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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that the data source is DefiLlama. It stops short of stating rate limits, latency, or what a success payload looks like, but the commercial/access terms are unusually well covered.

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?

Payment status is front-loaded in a single word ('Paid.') and the rest is dense, telegraphic, and waste-free. The fragments are slightly clipped and the raw endpoint URL is arguably redundant, which keeps it off a 5.

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 no-output-schema, no-annotation tool this covers the essentials: what data comes back, where it comes from, what it costs, and how to pay. The remaining gap is how results are shaped or paginated beyond the row limit, which is a minor omission rather than a blocking one.

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 all three parameters (sort, limit, min_tvl_usd) carry defaults and accepted values in the schema itself. The description adds nothing about sorting semantics, the meaning of the TVL floor, or the 1-100 row cap, so 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 — live DeFi yields for the kelp protocol, its pools across all chains — and enumerates the returned measures (APY, TVL, 7d APY change). Against a sibling set full of buy_yields_chain_*, buy_yields_token_* and buy_yields_protocol_* variants, the protocol scope is unambiguous.

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 resource name: an agent wanting kelp-protocol pool yields picks this. But there is no explicit when-to-use/when-not, no mention of how it relates to buy_yields_top, buy_yields_stablecoins, or the chain-level yield tools, and no guidance on whether the payment requirement should make the agent prefer a free alternative.

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