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

With no annotations, the description carries the full burden and does most of it: it declares the cost ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing rate limits, pagination, or the response envelope.

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-loaded with 'Paid.' and then the data description, followed by price, auth, and billing caveats — every sentence carries information. It is dense but not padded; only the trailing raw URL is arguably redundant with the tool name.

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 paid data-read with no output schema, the description names the returned metrics (APY, TVL, 7d APY change) and the data source, which is enough to call it correctly. The main gap is the exact response structure and ordering 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 coverage is 100% and all three optional parameters are documented in the schema, so the baseline applies. The description adds no extra meaning about sort ordering, limit bounds, or how min_tvl_usd filters rows.

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 resource ('Live DeFi yields for ether.fi-liquid') plus the exact payload ('its pools across chains with APY, TVL, 7d APY change'), which separates it from the chain-, token-, and other protocol-level yield siblings without needing the schema.

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?

Usage is only implied by the resource name. There is no explicit 'use this when you want protocol-level yields vs buy_yields_chain_* or buy_yields_token_*' routing, and no when-not guidance.

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