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 paid pricing ($0.005 USDC on Base or Solana), no account/API key required, that failed calls are not charged, and the upstream data source (DefiLlama). It stops short of stating data freshness, pagination, or typical result volume, which matters for a 'live pools' feed.

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-loads the cost flag ('Paid.') and then the capability, so an agent can triage spend first. The remaining clauses are dense but each is load-bearing (data source, price, payment chains, no-charge-on-failure, endpoint URL); the URL string is bulky but functional.

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?

No output schema exists, and the description adequately implies return content (pools, protocol, chain, APY, TVL). Combined with the pricing and access terms, an agent has enough to call this correctly; only the response shape/pagination detail is left unstated.

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 optional parameters (sort, limit, min_tvl_usd) are documented with defaults directly in the schema. The description mentions APY and TVL but adds no syntax, range, or default semantics beyond what the schema already supplies, 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?

States a specific outcome verb ('where to earn yield') and a precise resource scope ('live pools holding SPARKUSDC across protocols and chains, APY and TVL'), which cleanly distinguishes it from the many sibling buy_yields_token_*, buy_yields_chain_*, and buy_yields_protocol_* tools.

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?

The use case (find yield venues for one specific token) is implied clearly enough, and price/payment details help the agent decide whether to call. But there is no explicit when-to-use/when-not guidance and no routing to alternatives, e.g. whether to prefer buy_yields_protocol_sparklend or buy_yields_chain_base for overlapping queries.

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