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

With no annotations, the description must carry the behavioral burden. It does disclose the upstream data source (DeFiLlama), that chain and symbol have defaults (Base, USDC), and that TVL acts as a 'safety filter' — useful context. However, it omits return characteristics (does it return APY, TVL, pool addresses?), whether results are live or cached, any rate limits, and whether min_tvl is a hard exclusion.

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?

Two sentences, front-loaded with what the tool is and followed by what it returns and how it is filtered. Minimal waste, though the 'highest APY & yield radar' phrasing is slightly marketing-flavored rather than purely informational.

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?

All four parameters are optional with defaults and fully documented in the schema, and no output schema exists. The description names the result category ('top lending and liquidity pools') but does not describe the returned fields, so an agent cannot anticipate the response shape. Adequate but with a clear gap for a data-returning tool.

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 every parameter (chain, limit, symbol, min_tvl_usd) is already documented with type, range and default in the schema. The description reinforces the filtering semantics (token + chain + TVL) but adds no syntax or interpretation detail beyond what the schema provides, making the baseline 3 correct.

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 states a specific verb and resource: 'Finds top lending and liquidity pools for any token', with concrete examples (USDC, ETH, USDT, WBTC) and the filters it applies (blockchain, minimum TVL). This is clearly a DeFi yield scanner, distinct from every sibling tool (which are search, intel, audit and profiling tools), though the description never explicitly contrasts itself with them.

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 framing — use this when you want the highest-yield lending/liquidity pools for a token, optionally narrowed by chain and TVL. There is no explicit when-to-use statement, no prerequisites, and no named alternative for related questions (e.g. general token intelligence via token_alpha).

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