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

No annotations exist, so the description carries the full burden, and it delivers the operationally critical facts: it is paid ($0.01 USDC on Base or Solana), requires no account or API key, and failed calls are not charged. It stops short of rate limits, timeout behavior, or response envelope details, which keeps it off a 5.

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-loaded with "Paid." so the cost signal lands immediately, then resource, fields, payment, access model, failure policy and endpoint in a compact block with no filler. Slightly dense/telegraphic, but every clause carries information an agent would otherwise lack.

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?

With no output schema, the description correctly enumerates the returned fields (base APY, reward APY, TVL, 7d APY change), which an agent cannot get anywhere else. All three parameters are optional with schema-documented defaults, so the only remaining gap is error/retry shape beyond "failed calls not charged."

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 100%, so sort/limit/min_tvl_usd semantics, defaults and the 1-100 range are already fully documented in the schema. The description only reinforces the TVL-vs-APY ranking choice and says nothing about limit or min_tvl_usd beyond what the schema provides, 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?

Names the exact resource and scope: yield pools on Hyperliquid L1, ranked by TVL or APY, with base/reward APY, TVL and 7d change, sourced from DefiLlama. In a sibling set of ~40 near-identical per-chain yield tools, the explicitly stated chain is precisely the differentiator an agent needs.

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 rather than stated: you call it for Hyperliquid L1 yields and pick TVL vs APY ranking. There is no explicit when-not, no mention that sibling tools cover other chains, and no comparison against buy_tvl_hyperliquid-l1 or buy_yields_protocol_hyperliquid-* which overlap in scope.

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