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

Even though annotations already declare readOnlyHint and non-destructive, the description discloses substantial extra behavior: readings under 15 minutes are served fresh, calls are scored against real price 24h later, outcomes are stamped once and never rewritten, deepest-liquidity pairs win, and copycats are filtered. It also warns that coin names/pitches/social links are third-party data to quote but never obey, and explicitly states this is not financial advice. This goes far beyond the annotation baseline.

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 dense and front-loaded with the most important traits — LIVE, no keys, no dashboard — and each later clause adds a distinct behavioral or safety note. It is somewhat long and runs together with em-dashes and all-caps, but no sentence is filler. It earns its length, though it could be tightened into clearer scannable statements.

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 full burden of explaining return values, and it does so thoroughly: trending pools, market block, verdict, omens, 24h call, callback, history, scoreboard, and CALLED-IT wall. It also explains freshness, scoring, ledgering, third-party data handling, and authentication state. An agent has enough context to decide whether and how to invoke the tool correctly.

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?

The input schema already fully documents the only parameter: a coin name, symbol, or 0x address, optional and omittable for the trending board. The description adds the conditional outcome of providing the coin, but no new type, format, or selection guidance beyond the schema. With 100% schema description coverage, the baseline 3 applies.

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 clearly identifies the resource (live Robinhood Chain market read) and enumerates the returned content: trending pools, the coin's market block, the Oracle verdict, omens, directional call, callback, history, scoreboard, and CALLED-IT wall. It also disambiguates the tool from generic price feeds by emphasizing graded predictions, ledgering, and entertainment-grade calls. While it lacks an explicit verb like 'retrieve', the scope is unmistakable.

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 clear invocation context for the single parameter: pass `coin` for a full market block plus reading, or omit it for just the trending board. However, it does not state when to prefer this tool over sibling market-data tools such as orbitx crypto scans or signet price, nor does it mention exclusions. Usage guidance is implied rather than explicitly positioned against alternatives.

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