defi-yields

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

No annotations, so description must cover behavioral traits. It discloses keyless access and continuous updates, but omits rate limits, pagination behavior, and exact update interval. Adequate but not comprehensive.

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?

Four sentences, front-loaded with main purpose, then stats, then filter options, then output details. No wasted words, well-organized.

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?

Covers what the tool returns (APY breakdown, TVL, 7-day change, link) and filtering options. Lacks explicit return format and sorting direction, but enough for an agent to use. Missing some details like error handling for invalid chains, but overall complete.

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%, baseline 3. Description adds value by noting chain case-insensitivity, default TVL ($100k), and the ability to omit chain for all chains. Also hints at output fields like APY breakdown, but could provide more parameter synergy.

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 ('Returns'), a clear resource ('top DeFi yield pools ranked by APY from DeFiLlama'), and distinguishes from siblings like defi-yield-strategies by focusing on yield ranking and broad coverage.

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?

Provides clear context for when to use (ranking DeFi yields, filtering by chain/APY/TVL/stablecoins) and mentions no API key needed. Does not explicitly state when not to use or suggest alternatives, but the context is adequate.

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