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

Goes well beyond the annotations by disclosing that this returns ordered unsigned transactions (an approve only when the allowance is short, then depositLiquid with the Hyperlane fee as value), the 0.044 AERO-per-VELO rate, and that the AERO lands at the same address on Base. This is exactly the execution-model context annotations (readOnlyHint/idempotentHint) cannot convey.

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?

Front-loads the core action and follows with the transaction sequence, preconditions, and error taxonomy in a tight block. Density is high but every clause carries operational value; the error-reason enumeration is the only part that borders on long.

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?

An output schema exists, so return values need no explanation, and the description still covers the transaction shape, value/fee handling, chain restriction, account-vs-wallet precondition, and failure modes. Nothing an agent needs to invoke it correctly is missing.

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%, so 3 is the baseline; the description adds real meaning on top by naming the conversion rate and confirming the AERO recipient address is the owner_address. It does not restate format details (raw 18-decimal units) but the schema already covers those.

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?

Names a specific verb+resource+chain pair: upgrade VELO on Optimism to AERO on Base via the Velodrome migration. It also distinguishes itself from the sibling write_account_aero_upgrade by stating that VELO inside an Arcadia account is not handled here.

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?

Explicit preconditions and alternatives: use write_account_withdraw first if the VELO sits in an Arcadia account, the upgrade is optional because VELO stays usable, and it is Optimism (chain_id 10) only. It even decodes the 'upgrade unavailable' failure reasons so the agent knows when not to retry.

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