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

No annotations are provided, so the description carries full transparency burden. It discloses read-only behavior ('Reads only; you keep your keys'), refresh cadence (every 2 minutes), pricing ($0.02 per call over x402 with supported chains), non-advice disclaimer, and the two-step payment flow. The main gap is that it doesn't explain pagination or result limits beyond 'newest buys', but overall it's unusually thorough for a no-annotation tool.

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 description is front-loaded with the core resource and frequency, then moves to behavioral and payment details. It's dense but every sentence contributes something, with no obvious filler. Slightly long for a single-paragraph description, but structured well.

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 read-only, no-annotation, single-param tool with no output schema, the description covers purpose, scope, freshness, return fields, payment mechanics, and legal disclaimer. An agent has enough information to decide whether to call it and how to handle the payment flow. Nothing critical 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%, so the parameter `payment` is fully documented in the schema. The description adds context about how payment works (the terms-then-sign flow) and which assets are accepted, which complements the schema but doesn't add meaning beyond what's already covered. Baseline 3 is appropriate.

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 a specific resource and scope: newest buys by the 25 most profitable wallets of the last 24h, with size, time, wallet record and sell check. It is clearly distinguishable from sibling tools such as arc_whales or arc_fresh_launches, which don't promise copy-trade signals from profitable wallets.

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 gives a concrete usage procedure: call once without payment for terms, sign with your own wallet, call again with payment. That's clear and actionable. It doesn't compare against alternatives like arc_whales or arc_trust_check for evaluating wallet quality, but the procedural guidance is strong.

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