get_aave_flash_loans

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that flash loans must be borrowed and repaid in one transaction, and lists the return fields. It does not mention pagination, rate limits, or permissions, but for a read-only historical query tool, this is acceptable.

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 extremely concise: two sentences cover usage, return fields, and a behavioral constraint. Every sentence adds value, with no filler. The information is front-loaded for quick parsing.

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?

Given that there is no output schema, the description compensates by listing the return fields. It also explains the single-transaction nature of flash loans. It is complete enough for a list tool, though it could mention pagination limits (covered by 'first' in schema).

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%—both 'chain' and 'first' are described in the schema. The description does not add new meaning beyond the schema (e.g., it doesn't explain what 'first' does or how to use 'chain'). Baseline score of 3 is appropriate since schema already documents both parameters.

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 AAVE flash loans with specific fields (initiator, asset, amount, fee, timestamp). It includes example queries that help the agent match user intents like 'Show me recent flash loans on Ethereum'. This effectively distinguishes it from sibling tools like get_aave_borrows or get_aave_liquidations.

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 says 'Use this when the user asks about AAVE flash loans' and provides concrete query examples. While it does not list alternatives or when-not-to-use, the context is sufficient for an agent to differentiate from siblings like get_recent_borrows or get_aave_liquidations.

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