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

No annotations are supplied, so the description has to carry the burden; it does disclose the cost ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged, which is meaningful commercial context beyond the schema. It omits rate limits and any description of response shape 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?

Roughly four short sentences with no filler; pricing and access terms lead, then the purpose and the concrete endpoint. Every clause carries information an agent can act on.

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 read-only, zero-required-parameter lookup with full schema coverage and no output schema, the description gives enough: what data comes back, its source, cost, auth terms, and URL. Return format specifics are the only notable gap, and those are low-risk here.

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. The description adds only marginal value by naming APY and TVL as outputs, hinting at the sort dimension. No syntax or default detail is added 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 pools holding CBETH across protocols and chains, APY and TVL (DefiLlama data)' plus a concrete endpoint URL. The token is fixed by the name, and the description confirms it. It stops short of stating how it differs from the chain- and protocol-scoped yield 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?

'Where to earn yield on CBETH' implies the use case, but there is no explicit when-to-use or when-not guidance and no pointer to alternatives such as buy_yields_chain_base or buy_yields_protocol_lido for cross-token or single-protocol views. Usage is inferable but left to the agent.

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