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

Annotations already declare readOnly/openWorld and non-destructive, so the bar is lower; the description adds real value beyond them — counts only, wallets never identified (privacy), the exact fields returned, and a cost/auth model ($0.02 USDC on Base or covered by Alpha/Omega keys). No contradictions with the read-only annotation.

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?

Reasonably front-loaded with the core definition, but the dense single-sentence style is hard to parse and the pricing statement is duplicated ('Included on Alpha and Omega keys; otherwise $0.02 USDC on Base' then again in parentheses). One redundant sentence costs it.

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, the description carries the return-shape burden and does list the fields (wallets, buys, WETH, first/last buy, template_launch). Privacy, cost, and framing caveats are covered, leaving only 'template_launch' under-explained.

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 description coverage is 100%, with all four parameters documented, and the description merely restates the same defaults (60 minutes, 3+ wallets, 0.05+ WETH). Baseline 3 is appropriate since the schema does the heavy lifting.

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: tokens that multiple distinct wallets bought within a window, drawn from the RobinX wallet tape, with returned fields listed. It is genuinely distinguishable from generic signal siblings, though it never names a specific alternative tool to route against.

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 operational defaults and a caution ('An observation about buying, not a signal to trade'), which implies the intended framing. But it never says when to prefer this over apparent neighbors like robinx_smart_holders, robinx_pulse, or robinx_signals, leaving the routing decision to inference.

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