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

With no annotations, the description carries the full burden and does well: it discloses hourly refresh, the exclusion of launch insiders and bot-like wallets, the indexed pool scope (USDC pairs), the $0.01 price, accepted currencies, and the x402 auth flow. It omits return shape and rate-limit behavior, so it is strong but not exhaustive.

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 ranking definition, followed by scope/exclusions and payment mechanics. Every sentence earns its place, though the payment paragraph is dense and could be split more cleanly.

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 or annotations exist, so the description must do the work, and it covers data scope, refresh cadence, exclusions, cost, and the auth flow. It stops short of describing the exact response structure, but for a paid listing tool it is largely 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?

Schema coverage is 100%, so the single `payment` param is documented structurally, but the description adds real meaning beyond the schema by explaining how the signed payload is obtained and that passing it completes the purchase in-call.

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: 'Arc wallets that made the most REALISED profit in the last 24 h (closed trades only, average cost)', plus the returned fields (win/loss, open cost, latest buys). This clearly separates it from siblings like arc_wallet or arc_pools.

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 two-step payment flow ('call once without payment for the terms, sign them, call again with payment') gives operational guidance, but there is no explicit statement of when to choose this ranking over sibling tools such as arc_pools or arc_fresh_launches.

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