prepare_aave_borrow

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

Annotations show destructiveHint=true and idempotentHint=true, but the description adds critical behavioral context: stable rate borrows revert on production markets, and the borrower must have collateral. This goes beyond annotations by disclosing a deprecated functionality that could cause failures.

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 concise sentences: the first explains the core action and a critical caveat, the second adds a prerequisite. No redundant information, every sentence adds 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 description does not specify the output format (e.g., unsigned transaction payload details) and has low parameter coverage. However, for a transaction preparation tool with clear sibling context, it is adequately complete for basic usage, though missing output description is a gap.

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 description coverage is only 25% (only the 'amount' parameter has a description). The description repeats the 'max' option already in the schema but does not explain 'wallet', 'asset', or 'chain' parameters beyond what the schema provides. This fails to compensate for low schema coverage.

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 builds an unsigned Aave V3 borrow transaction, specifies variable rate, and notes stable rate is deprecated. This distinguishes it from sibling tools like prepare_aave_repay or prepare_aave_supply.

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 mentions a prerequisite (sufficient collateral) but does not explicitly state when to use this tool versus other borrow preparation tools (e.g., prepare_compound_borrow) or provide criteria for exclusion. Usage context is implied but not comprehensive.

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