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

No annotations are provided, so the description carries the full burden and does substantial work: it discloses the payment model ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the upstream data source. It stops short of describing pagination behavior, rate limits, or the response shape, which matters for a paid endpoint.

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?

Four compact fragments, front-loaded with the payoff and followed by cost, access terms, and endpoint URL. No sentence is redundant and the key constraint (paid, $0.01) appears before the call details.

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 summarizes what comes back (pools, APY, TVL) and covers the commercial/access prerequisites that an agent must know before calling a paid endpoint. The main residual gap is return shape and volume of rows, which is only partly covered by the limit parameter in the schema.

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 in the schema itself. The description adds no syntax, default, or interaction detail beyond that, so the baseline 3 applies. Note the description never mentions that results are filterable by TVL or sortable.

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 clearly states the resource and the returned content: live yield pools holding USYC across protocols and chains, with APY and TVL sourced from DefiLlama. It is specific enough to separate this from generic chain- or protocol-level yield tools, though it never names the closest sibling (buy_yields_protocol_circle-usyc) to draw the boundary explicitly.

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?

"Where to earn yield on USYC" implies the use case (finding USYC-denominated yield opportunities), but there is no explicit when-to-use, when-not-to-use, or pointer to the alternative token- or protocol-scoped yield tools. Usage is inferable rather than stated.

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