get_defi_rates

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the purpose and usage, but does not disclose side effects (e.g., read-only, no mutations), authentication needs, rate limits, or error conditions. This is a significant gap for a data-fetching 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 sentences, no wasted words. Purpose and usage are front-loaded efficiently. Every sentence contributes value.

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 tool has one optional parameter and no annotations or output schema. The description provides purpose and usage but does not explain the return format, possible errors, or default behavior when chain_id is omitted. For a simple data retrieval tool, this is marginally adequate but could be more 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% with a clear description of the optional chain_id parameter. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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?

Description clearly states it returns supply and borrow APY rates for major assets on Aave V3. The verb 'returns' and specific resource 'supply and borrow APY rates' combined with platform 'Aave V3' make the purpose unambiguous and distinct from siblings like deposit_aave or withdraw_aave.

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 explicit usage guidance: 'Use this to decide where to deploy capital for yield.' This tells the agent when to invoke the tool. However, it does not mention when not to use it or alternative tools (though no direct alternative exists among siblings).

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