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

No annotations are supplied, so the description carries the full burden and does so: it discloses the ranking methodology and its anti-manipulation rationale ('two-way wallet farms do not top it'), the active filter that drops unsellable/launch-and-pull pools, the returned fields, the price ($0.001 per call), accepted payment rails, and the two-call x402 handshake.

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 the core answer and ordered sensibly: what it shows, how it ranks, what it excludes, what it costs and how to pay. Dense but mostly earning its space; the final sentence compresses pricing, rails, and the two-step flow into one long clause that could be split for faster scanning.

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 and no annotations, the description still tells the agent what comes back (volume, buys, sells, price change, pool age) and exactly how the paid invocation works. Nothing an agent needs to decide to call it, or to complete payment, is missing.

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% for the single `payment` parameter, so baseline is 3, but the description adds meaning beyond the schema: it explains the first call is unauthenticated and returns terms, and that the signed payload only completes the purchase when passed on the second call. That sequencing is not derivable from the schema alone.

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 resource and moment ('what is trending on Arc right now') plus the exact ranking rule (NET USDC inflow, buys minus sells, over 1h and 24h) and the data universe (every Uniswap v4 pool). This clearly separates it from siblings such as arc_fresh_launches (recency) or arc_whale_feed (individual trades).

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?

Gives clear invocation guidance: 'No input', call once without `payment` to obtain terms, sign with your own wallet, call again with `payment`. It also states the exclusion condition (tokens failing the live sell test). It does not, however, name a sibling alternative for when trending inflow is the wrong lens (e.g. arc_pools or arc_price), so routing guidance is implicit.

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