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

Annotations only cover readOnlyHint and openWorldHint; the description adds materially important behavior beyond them — paid per call at 0.55 USDC on Base via x402, latency ('Seconds'), and the explicit reassurance that nothing is executed. The 10% fee set-aside and identity/verification links are transparency-adjacent but more promotional than operationally useful.

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 value proposition is front-loaded, which is good, but a substantial share of the text is promotional: token contract address, ERC-8004 agent ID, Virtuals ACP link, and payout wallet. Those sentences serve trust verification for a paid endpoint but crowd out parameter and output detail.

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 output schema, the description does carry the return-value burden and lists the five result categories an agent will receive. Missing only response shape/pagination detail and error behavior; payment terms and safety profile are fully covered.

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?

With 50% schema description coverage, the description names all four parameters and marks bridge_amount optional, plus supplies a concrete example object showing chain/token casing. However, it adds no semantics for the two enum chain parameters beyond the example, and does not explain the default ~$1000 amount logic that lives in 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 specific verb and resource — pick a bridge route — and enumerates the concrete evidence it returns (LI.FI/Across quotes ranked by cost and ETA, TVL trends, incidents, canonical-bridge timing, L2BEAT risks). No sibling tool in the list covers bridging, so the scope is unambiguous without needing differentiation.

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?

'Pick a cheaper, safer bridge route before moving funds' implies the usage context (pre-bridge planning) but never states when not to use it, what prerequisites exist, or how it relates to adjacent tools like gas_fee_timing or contract_security_scan. Guidance is implied rather than explicit.

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