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

With no annotations, the description carries the full burden. 'Read' plus 'right now' usefully signals a non-destructive, live-snapshot operation, and 'Every key carries its unit' discloses output formatting. However, it says nothing about freshness/staleness guarantees, rate limits, or failure behavior for non-token addresses.

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-loaded with the verb and resource, then the field list, then the usage trigger. The field enumeration is long but each item is substantive and tells the agent what data is available. No filler sentences.

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?

No output schema exists, so the description must describe return values — it does so thoroughly by enumerating fields and noting that each key carries its unit. Remaining gaps are behavioral (rate limits, error cases) rather than about what the tool returns.

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?

There is a single parameter and schema description coverage is 100% — the schema already specifies '0x followed by 40 hex characters.' The description adds no address-specific semantics, so the baseline of 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 names a specific verb ('Read') and resource ('Robinhood Chain token') and enumerates the returned fields (name, supply, owner powers, price, liquidity, etc.), so the agent knows exactly what it gets. It does not explicitly contrast itself with robinhood_radar or trace_wallet, but those target different resources (radar and wallet tracing), so confusion risk is low.

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?

It gives an explicit trigger: 'Use it whenever the user mentions a token contract address.' That is a clear when-to-use condition. It stops short of stating when NOT to use it or naming alternatives, so it is not a full 5.

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