prepare_aave_withdraw

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

Annotations already indicate destructiveHint=true (modifies state) and idempotentHint=true. The description adds that it builds an unsigned transaction, implying no immediate effect. It doesn't elaborate on any side effects or authorization needs, but the safety profile is adequately covered by annotations.

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 with zero wasted words. It delivers the core purpose and a key usage tip immediately. No unnecessary elaboration.

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 the tool's simplicity and the presence of annotations describing its safety profile, the description covers essential behavioral aspects. It lacks details on the output format or typical flow, but for a transaction preparation tool, the provided information is generally sufficient.

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 covers parameters, but only 'amount' has a description. The description adds meaningful guidance by explaining the 'max' value for amount, which is not obvious from the schema alone. For other parameters, the schema provides enough via patterns and enums.

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 it builds an unsigned Aave V3 withdraw transaction, which is specific to withdrawing. It also highlights the special 'max' amount option. Among sibling tools like prepare_aave_borrow or prepare_aave_supply, this is distinctly different.

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 indicates when to use (for withdrawing from Aave) and provides a usage tip for 'max'. However, it does not explicitly contrast with other Aave operations or mention prerequisites. The context is clear but could be more explicit.

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