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

With no annotations, the description carries the full disclosure burden and does reasonably well: it discloses that quotes are a fixed 2 USDC probe (not a full transfer), that they refresh every 10 minutes, the source-chain coverage, the 11 USDC X1 bridge minimum, and that CCTP is only noted rather than quoted. It does not state whether it is read-only (it plainly is, but that is inferred), nor the response shape.

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?

Everything is packed into one long sentence with semicolons and embedded parentheticals, so the information is present but hard to scan. The core point (measured bridge quotes onto Arc) is front-loaded, but the clause about the X1 minimum and the CCTP note would be clearer as separate, shorter statements.

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?

There is no output schema and no annotations, so the description must convey what comes back, and it does name the three things an agent needs: what arrives, the cost, and the time. Coverage of chains, quote size, refresh cadence, and the X1 and CCTP caveats makes it complete enough to call correctly, with only the exact response shape unspecified.

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 tool takes zero parameters, which is the baseline 4 case; the description is consistent with that, since chain coverage is described as fixed and automatic rather than selectable. No parameter meaning is needed or missing.

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 states a specific verb and resource: showing measured rates for getting USDC onto Arc (eip155:5042) from other chains via LI.FI, plus the X1 and CCTP paths. It is clearly a rate-discovery tool, not a transaction tool. However, it does not distinguish itself from the extremely similar sibling get_onto_arc, which an agent could easily pick instead.

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?

It gives one usage cue: 'Use it to bring an agent or a person to Arc from wherever they are, then claim at the faucet', which implies the pre-faucet funding step. There are no exclusions or explicit alternatives, and the near-duplicate get_onto_arc and the related arc_cctp_cost / arc_exit_check siblings are never mentioned, so routing between them is left to inference.

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