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

With no annotations, the description carries the full burden and does substantial work: it discloses the x402 payment flow (402 with PAYMENT-REQUIRED header, retry with PAYMENT-SIGNATURE), the exact cost, where payment goes in `params._meta`, and that results are ordered by relevance. It omits error/no-match behavior and rate limits.

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?

Front-loaded with purpose and structured in labelled bullets (Cost, Key inputs, Returns, Next) that scan well. Slightly overlong: the 0.005 USDC cost is stated twice in different units, adding mild redundancy.

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?

No output schema and no annotations, so the description must stand alone; it summarizes return contents (verification status, safety verdicts, pools) and the downstream handoff. It leaves out failure modes and whether results are paginated, which is a modest gap.

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 0%, so the description must compensate, and it does: it marks `query` as required, specifies `limit` range 1-25 and default 10, and — most valuably — expands the semantic space of `query` to ticker, name, prefix or 0x address, which the bare string schema does not convey.

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 first sentence gives a precise verb (resolves) and resource (ERC-20 tokens on Arc) plus the accepted input forms (ticker, name, prefix, 0x address). It is clearly distinguishable from tradeQuote/tradeSwap siblings, though it never explicitly says how it differs from other search-like tools.

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?

The description states the enabling context (resolve a token before trading) and the explicit next step: pass the chosen result's `address` as `sell` or `buy` to POST /trade/v1/quote. No when-not-to-use guidance is given, which holds it below a 5.

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