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

No annotations exist, so the description carries the full behavioral burden, and it does add real value: price ($0.005 USDC on Base or Solana), no account/API key, failed calls not charged, and the upstream data source (DefiLlama). It stops short of return shape, ordering behavior, or data freshness beyond the word 'Live', leaving meaningful gaps for a paid data tool.

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 purpose, then cost, then access constraints, then endpoint. Dense and free of filler; every clause carries operational information.

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 annotations and no output schema, the description must cover both behavior and return content, and it largely does — payment, auth, billing on failure, data source, and returned fields. Missing only the response envelope/pagination shape an agent might want before paying.

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%, so sort, limit, and min_tvl_usd are already documented with defaults. The description's mention of APY/TVL/7d change loosely maps to the sort options but adds no syntax or default detail beyond the schema — the baseline 3 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?

States a specific resource ('Live DeFi yields for binance-staked-eth') and enumerates the returned metrics (APY, TVL, 7d APY change). A reader can tell this is the protocol-level sibling of the chain/token yield tools, though the description never explicitly contrasts itself with buy_yields_chain_* or buy_yields_token_* endpoints.

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 implied by the name and by 'its pools across chains' — call this when you want yield data scoped to this one protocol. There is no explicit when-to-use/when-not or routing advice toward the chain, token, or top-level yield alternatives, so the agent must infer the boundary.

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