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

No annotations, so the description carries the burden. It usefully discloses the LI.FI dependency and the '$0.01 USDC per call' cost, which an agent must know before invoking. However, it never states that this only returns a quote rather than executing a bridge transaction, nor anything about slippage, route expiry, or failure modes — significant omissions for a paid, unannotated tool.

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 short sentences, front-loaded with purpose then scope then the scan shortcut then price. No filler; the cost disclosure is placed last where it acts as a final precondition check.

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?

With no annotations and no output schema, the description does the heavy lifting well: it names the provider, the comparison outputs, supported assets and chains, the scan mode, and the per-call price. The remaining gap is that an agent cannot tell from the description whether a call performs any on-chain action or what the returned route object looks like.

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 baseline is 3; the description adds value by listing supported tokens (ETH, USDC, custom token addresses) and the supported chain set beyond the schema's 'e.g.' examples, plus reiterating the 'scan' sentinel for toChain. It still says nothing about the 'amount' string format, leaving that entirely to the schema.

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+resource ('Find the optimal cross-chain bridge route') plus the data provider (LI.FI) and the comparison dimensions (fees, speed, output). The 'cross-chain ... any chain pair' scoping separates it from the same-chain swap_quote sibling without needing to open either schema.

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?

'Compare fees, speed, and output across bridges' and the toChain='scan' tip give clear when-to-use guidance for route comparison and L2 scanning. It stops short of naming a when-not or an explicit alternative (e.g. swap_quote for same-chain swaps), so it is clear context rather than full routing guidance.

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