Best rate for one asset

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

Beyond the read-only annotations, it discloses that junk-farm filters are applied, that the tool ranks by rate alone, and that fees and rate durability should be checked elsewhere. It leaves minor gaps around exact filter thresholds and no-result 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?

The purpose is front-loaded in the first sentence, and each subsequent sentence adds useful routing or caveat information. There is no redundant repetition of the title or schema.

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 simple one-parameter lookup with read-only annotations, the description explains what is returned at a high level, how results are filtered, and what to verify before acting. It could be slightly more complete by mentioning fallback behavior when no pool qualifies.

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 the single `asset` parameter is already well documented as an asset symbol. The description adds only the framing that the asset is the subject of a 'best rate for X' question, 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?

The description states a specific verb and resource: it returns the single highest-APY pool on Base for one asset, with explicit filtering. This clearly distinguishes it from list-oriented siblings such as list_base_yields and list_lending_vaults.

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?

It gives a clear use case ('where is the best rate for X') and names follow-up tools (`market_profile`, `yield_history`) before committing capital. It does not explicitly state when not to use it or compare it directly to list_base_yields as an alternative.

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