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

With no annotations, the description carries the burden and does meaningful work: it discloses that the output is an unsigned transaction (not a signed/broadcast one), that a 30 bps integrator fee is embedded, that each call costs 0.001 USDC via x402, and that LI.FI Composer executes the route. It does not cover token approval requirements, failure/refund behavior, or whether the quoted rate is final.

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?

Four dense sentences, front-loaded with the core action and output type before fees and payment mechanics. Every sentence carries operative information an agent needs (output form, fee, payment flow, execution venue); nothing is padded.

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?

For an 8-parameter, no-annotation, no-output-schema tool that spends real money, the description covers output type, cost structure, and payment protocol well. It leaves gaps around approval steps, slippage/default behavior implications, and what the unsigned transaction payload contains.

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 the baseline is 3; the description earns an increment by explaining where vaultToken comes from (earn-vaults lpToken.address) and by framing the call's inputs as a swap-bridge-deposit pipeline. The payment/402 mechanics also contextualize the optional paymentProof parameter beyond its schema text.

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?

States a concrete verb chain and resource: returns an unsigned EVM transaction that swaps + bridges + deposits into a vault in one step. It implicitly routes to the earn_vaults sibling by specifying that vaultToken comes from earn-vaults lpToken.address, which differentiates it from swap_quote_and_build. It stops short of naming an alternative explicitly, so not a 5.

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?

Clearly scopes usage: cross-chain deposit from any chain into any vault, with the token-address sourcing rule pointed at earn_vaults. The payment sequencing (omit paymentProof on first call, receive 402 instructions, retry with proof) tells the agent exactly how to drive the call. No explicit "when not to use this / use X instead" clause.

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