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

With no annotations, the description carries the full behavioral burden and largely fails it. It does not say whether this is a read-only informational lookup, whether it requires a wallet or signature, whether the output is static documentation or live-queried data (only 'bridges measured live' hints at the latter), or what the trailing 'Free.' refers to — the tool call, the faucet claim, or the routes generally.

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 single run-on sentence packs a useful inventory but is not front-loaded: the purpose is buried under a six-item content list joined by em-dashes. The dangling one-word 'Free.' adds ambiguity rather than value, and the sentence would be stronger split into a purpose statement plus a compact route summary.

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 a zero-parameter informational tool with no output schema, the description gives an adequate topical map of what the answer covers. It is incomplete on the essentials an agent needs — return format, whether data is live, and whether any wallet setup is a prerequisite — so it is minimum viable rather than complete.

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, so the baseline is 4 and there is nothing for the description to compensate for. The description's route list is content preview, not parameter documentation, but no parameter semantics are needed here.

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 names the resource (routes for getting USDC onto Arc) and enumerates its contents (faucet, bridges, CCTP, Gateway, Onramp Kit), but never states what the tool actually returns or does. It reads as a content inventory rather than a verb-plus-resource definition, and it does not differentiate itself from siblings like arc_faucet_claim, arc_bridges, or arc_cctp_cost that cover the same topics individually.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no alternatives named. The phrase 'for apps that let people pay by card or Apple Pay' describes one route's audience, not when an agent should call this tool instead of the more specific faucet, bridge, or CCTP tools.

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