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

With no annotations, the description carries the burden well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged, plus the DefiLlama data source. It doesn't cover rate limits, response format, or pagination behavior, which keeps it from 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?

Very compact: payment gating is flagged first with 'Paid.', the purpose and data fields follow, then cost/access terms. Every sentence carries information an agent needs (cost, auth, failure billing) and nothing is repeated from structured fields.

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 zero-required-parameter read tool with no output schema, the description covers what the agent needs: what the data is, its source, the cost and payment chain, and that failures aren't billed. The one gap is that the exact response shape (per-pool fields vs. aggregate) is only loosely sketched.

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, and min_tvl_usd are already documented in the input schema. The description mentions the returned data fields (APY, TVL, 7d APY change) but adds no meaning about parameter syntax or defaults, so the 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?

The description names a specific verb and resource: live DeFi yield data for the solv-basis-trading protocol, with its pools across chains and the APY/TVL/7d-change fields returned. It doesn't explicitly name which sibling to use instead (e.g., buy_yields_chain_* or buy_yields_token_*), so the differentiation is implied by the protocol-scoped name rather than stated.

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 protocol-specific framing, but there's no explicit when-to-use/when-not guidance, no mention of alternatives for chain-level or token-level yield lookups, and no prerequisites stated. An agent can infer the scope from the name but must reason about which of the many yields siblings to pick.

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