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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuine context beyond them: data provenance ('from NLYRA's own node') and freshness ('live read'), plus the fact that every entry carries a Risk Level. It omits refresh cadence, caching, and error behavior.

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?

A single sentence that front-loads the core concept ('A live read of Robinhood Chain from NLYRA's own node') before the em-dash list of returned data. Every clause earns its place, especially since there is no output schema to document the returns elsewhere.

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 zero-parameter, no-output-schema dashboard tool, the description adequately covers what an agent gets back by enumerating the surfaced metrics and the Risk Level annotation. It is complete enough to call correctly, though it could state freshness/refresh expectations for a 'live' feed.

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 tool takes zero parameters, so there is no parameter semantics to document — the rubric baseline for 0 params is 4. The description's enumeration of return fields is useful but relates to output, not inputs, and no output schema exists.

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 uses a concrete verb ('live read') plus a specific resource ('Robinhood Chain') and enumerates exactly what the tool surfaces: TPS, hourly volume, biggest movers, most traded tokens, newest launches, each with a Risk Level. This scope clearly sets it apart from the token-scoped siblings (check_token_risk, find_token) and trade-prep siblings, though it never names an alternative explicitly.

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?

There is no explicit when-to-use or when-not-to-use statement, but the enumerated market-wide content strongly implies the use case (a market snapshot rather than per-token or trade actions), which contrasts implicitly with the siblings. Guidance is inferable but not stated.

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