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

With no annotations provided, the description supplies valuable operational details: the exact price, USDC payment on Base or Solana, no account or API key requirement, no charge for failed calls, and the data source. The wording implies a read-only lookup, but it does not explicitly address update cadence, rate limits, or other response and error 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?

The description is compact and front-loads the paid nature and precise data scope, followed by cost, access, failure-billing, and endpoint details. Each short statement contributes useful information without substantive filler.

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 simple lookup with three fully documented optional parameters and no output schema, it adequately describes the returned data, scope, source, price, access requirements, and endpoint. It would be more complete with explicit sibling-routing guidance and details such as data freshness or empty-result behavior.

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 the three optional parameters already document sorting choices, row limits, TVL filtering, and defaults. The description adds no further parameter syntax or interaction details, so the high-coverage baseline 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?

The description clearly identifies live DeFi yield data for zerobase-cedefi, covering its pools across chains and the key fields: APY, TVL, and 7-day APY change. Naming DefiLlama as the source adds specificity, but the description does not explicitly differentiate this tool from the other yield-related siblings.

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 protocol-specific, cross-chain scope implies when the tool is useful, but there is no explicit selection guidance. It does not explain when to choose it over buy_yields_chain_*, buy_yields_token_*, buy_yields_stablecoins, or buy_yields_top.

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