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 that the call is paid at $0.002 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged — a genuinely important failure-semantics detail. It also names the upstream data source and the concrete fields returned, though it omits rate limits and any response-size or pagination 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?

A single dense, front-loaded block: cost first, then purpose, then data fields, then payment terms and endpoint. Every element carries information an agent needs, and nothing is padding, though the telegraphic run-on style mixes pricing and purpose in a way that is slightly harder to scan than clean sentences.

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 annotations and no output schema, the description supplies the missing pieces: it enumerates the returned metrics and states the payment prerequisites and failure-cost policy. Only the absence of rate-limit and pagination/row-cap behavior keeps it from being fully complete.

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 each of the three optional parameters is already documented in the schema, making 3 the baseline. The description adds marginal meaning by tying 'top pools by TVL or APY' to the sort choice and by naming TVL as a returned metric, but says nothing extra about limit bounds or the min_tvl_usd default.

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 resource and scope: live DeFi yields on Rootstock, top pools ranked by TVL or APY, with named output fields (base/reward APY, TVL, 7d APY change) and a data source (DefiLlama). The chain qualifier in 'Rootstock' separates it from the dozens of buy_yields_chain_* siblings, and the focus on pool yields distinguishes it from buy_tvl_rootstock.

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: an agent can infer this is the tool for pool-level yields on Rootstock. However, it never says when to prefer it over buy_tvl_rootstock, buy_yields_protocol_*, buy_yields_top, or buy_yields_token_*, nor does it set any exclusion. The 'Paid' framing gives cost context for a go/no-go decision but does not route between alternatives.

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