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

With no annotations, the description carries the burden well: it discloses price ($0.003/call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the fresh-launch nature of the data, and the sampling methodology (first 60 swaps of the first two minutes, earliest 12 buyers). It omits any statement about rate limits, latency for the 'real time' claim, or the exact shape of the verdicts returned, which keeps it from a 5.

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 core purpose is front-loaded and every sentence carries information (methodology, evidence location, price, payment flow). The long parenthetical about the first 60 swaps and 12 buyers is dense and slightly run-on, costing a little readability without being padding.

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 one-parameter tool with no output schema, the description covers what the tool returns (launches with sell and bundle verdicts), where to verify the evidence, and the full payment mechanic. The main remaining gap is not describing the return payload's shape or volume, but that is a modest omission given the otherwise thorough coverage.

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 already 100% for the single `payment` parameter, so the schema baseline would be 3. The description earns the extra point by explaining the operational semantics the schema cannot: call once without `payment` to receive terms, sign with your own wallet, then call again with the signed payload — turning a bare string field into a documented handshake.

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 verb+resource ('Arc launches in real time') plus the two value-adds an agent cares about: a sell verdict from a real round trip and a bundle verdict. It names the sibling that holds the underlying evidence (arc_bundle_check), so an agent can distinguish this from arc_trending, arc_pools, or arc_bundle_check itself without opening a schema.

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 qualifying clause 'so you see the new pools that can actually be exited' tells the agent the selection condition, and the payment instructions give an explicit two-step call protocol. It does not explicitly contrast against the nearest alternatives (arc_trending, arc_pools, arc_exit_check), so an agent still has to infer which one to prefer for non-fresh-pool queries.

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