get_defi_rates

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

No annotations are provided, so the description must disclose behavioral traits. It does not indicate whether the tool is read-only, has rate limits, data freshness, or any side effects. For a data-fetching tool, the lack of such details reduces transparency.

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 description is two sentences, with no redundant phrases. The first sentence states the core functionality, and the second provides usage guidance. It is concise and well-structured.

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?

The description adequately covers the tool's purpose and usage for a simple rate-fetching tool with one optional parameter. However, it could be improved by clarifying what 'major assets' includes or data freshness, but overall it is sufficient for the complexity level.

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?

The input schema has 100% description coverage for the single parameter chain_id, but the tool description adds no additional context beyond the schema. It does not list valid chain IDs or explain the behavior when chain_id is omitted (the parameter is optional). Baseline 3 is appropriate as schema covers the basics.

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 clearly states the tool returns current supply and borrow APY rates for major assets on Aave V3. The verb 'returns' and the specific resource 'supply and borrow APY rates' make the purpose unambiguous. It distinguishes from sibling tools like deposit_aave and withdraw_aave, which are transactional.

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?

The description explicitly advises using the tool to decide where to deploy capital for yield, providing a clear use case. However, it does not mention when not to use it or compare it with alternative tools (e.g., get_token_price for yields), which would be helpful but is not critical given the unique purpose.

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