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

Annotations already cover safety (readOnly, non-destructive, openWorld), so the bar is lower; the description adds real value beyond them: the paywall ($0.05 USDC on Base vs. an Omega key), the idempotent echo-counting rule, that rooms are counted but never named, and the exact output fields (verdict, launch template, LP custody, depth, +1h/+6h/+24h outcome). Missing: pagination/cursor behavior and rate-limit context.

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-loads the core definition and packs the criteria into one dense paragraph with no filler. The closing parenthetical repeats the pricing already stated one clause earlier, which is minor waste but the only real redundancy.

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-value burden and does so by enumerating the receipts, checks, and measured outcomes a signal contains. Payment mechanics are covered; only cursor/pagination behavior is left unexplained.

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 all four parameters are already documented in the schema; baseline is 3. The description paraphrases the flag-check semantics behind exclude_flagged but adds no syntax, format, or defaults beyond what the schema provides.

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?

Names the resource (Robinhood Chain tokens) and the exact convergence rule (≥1 X call + ≥3 Telegram rooms within 60 minutes), which is far more specific than the title alone. It implicitly separates itself from siblings like robinx_signals or robinx_tg_first_call by stating its own detection criteria, though it never names an alternative tool.

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?

States 'An observation, not a trade call' and discloses the cost, which frames intent and commitment. But it gives no guidance on when to prefer this over robinx_signals, robinx_social_momentum, or robinx_tg_first_call, and no exclusion conditions.

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