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

With no annotations, the description carries the full burden: it establishes this is a read-only listing on Base and names the fields returned, which is useful. It says nothing about data freshness, result-size limits/pagination, or whether the list is exhaustive across protocols, which matter for a discovery 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?

Two short sentences with zero filler; the resource and scope come first and the filter note trails it. Nothing could be cut without losing 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?

For a read-only list tool with four optional, fully documented parameters and no output schema, the description covers chain, domain, and returned fields adequately. Only ordering/limit behavior is left unstated, a minor gap given the simplicity.

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 all four filters (asset, minTvl, stable, sortByApy) are already documented one level down. The description adds only a generic 'Optional filters' and the returned-field list, so baseline 3 is appropriate.

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 verb ('List') and resource ('staking/lending yield opportunities on Base'), and previews the returned fields (APY, TVL, project). It does not explicitly contrast itself with siblings best_yield or list_lending_vaults, so differentiation is only implied by 'List' vs 'best'.

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?

'Optional filters' hints that the tool accepts narrowing criteria and works fine with no arguments, but there is no explicit when-to-use guidance, no statement of when to prefer best_yield or list_lending_vaults, and no exclusions.

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