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

With no annotations, the description carries the burden and does well: it discloses that the call is paid ($0.005 USDC on Base or Solana), that no auth is required, that failed calls are not charged, and that data comes from DefiLlama. It omits return shape and any rate limits, 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?

Three tight sentences, front-loaded with the 'Paid.' signal and then the capability, followed by the commercial terms. The trailing URL is arguably redundant but plausibly useful as an HTTP fallback; nothing else is padding.

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, so the description must convey return content, and it does so at a high level (pools across chains with APY, TVL, 7d APY change). For a read-only, zero-required-parameter paid endpoint this is nearly sufficient; only the response envelope and empty-result behavior are 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%, so sort, limit, and min_tvl_usd are already documented in the schema. The description mentions the fields available (APY, TVL, 7d APY change), which loosely maps to the sort options but adds no default or format detail beyond the schema.

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?

Names a specific resource and scope: 'Live DeFi yields for securitize-tokenized-aaa-clo-fund: its pools across chains with APY, TVL, 7d APY change'. The protocol-specific naming distinguishes it from the chain/token yield siblings, though the description itself never says so 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?

The description covers payment and access conditions (cost, no account, no API key, failed calls free) but gives no guidance on when to choose this protocol-level yields tool over the chain_ or token_ yield siblings. Usage is implied by the protocol embedded in the name rather than stated.

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