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

With no annotations, the description carries the full burden and does well: it discloses pricing ($0.01 USDC on Base or Solana), that no auth is needed, that failed calls are not charged, and that data comes from DefiLlama. It also enumerates the returned metrics, which is more than most paid-endpoint definitions offer. It stops short of rate limits, latency, or response envelope details.

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 and dense: the 'Paid.' flag comes first, followed by content, price, auth, billing, and endpoint URL, with no filler sentences. The trailing URL is mildly redundant with the tool name but is plausibly useful data rather than waste.

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 3-optional-parameter, no-output-schema, paid endpoint, the definition covers cost, access model, failure billing, data source, and returned fields — enough for an agent to decide and call correctly. Only secondary operational details (rate limits, row shape) are absent.

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 the schema already documents sort, limit, and min_tvl_usd. The description echoes 'by TVL or APY' but adds no format or interaction detail (e.g. how min_tvl_usd interacts with sorting, or that limit caps rows at 100); 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+resource ('Live DeFi yields on Base') and the exact content returned ('top pools by TVL or APY with base/reward APY, TVL, 7d APY change'). The chain scoping in the description cleanly separates it from the many sibling buy_yields_chain_* tools, which cover other chains.

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 chain name and by 'top pools by TVL or APY', which hints at how to pick a sort order. But there is no explicit when-to-use guidance, no mention of when to prefer buy_yields_protocol_* (protocol-level yields) or buy_tvl_base instead, and no statement of prerequisites beyond 'no account, no API key'.

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