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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the address format ('0x + 40 hex') and that wallet identifiers 'come as prefixes', which tells the agent how to interpret output. No rate-limit or auth notes, but those are not critical here.

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 what the tool returns, followed by two short routing sentences. The field enumeration is dense but each field earns its place; no filler, though the single long opening clause is heavy.

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 enumerates the returned fields in detail, and it documents the input format and the wallet-prefix convention. An agent has enough to call it correctly and anticipate the response shape, leaving only minor gaps around overlapping sibling tools.

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 0%, so the description must compensate, and it does: it specifies the single 'address' param as '0x + 40 hex'. That format constraint is meaningful semantics beyond the bare string schema.

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 resource ('One Robinhood Chain token (0x + 40 hex)') and enumerates exactly what it returns: market cap, liquidity, volume, 24h buys/sells, official-stock-token flag, developer launch record and funder record. It also distinguishes itself from rh_token_safety and rh_swaps, so an agent can identify it without opening the schema.

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 explicitly routes the agent to alternatives with conditions: 'For flags and sellability use rh_token_safety; for trades use rh_swaps.' That is clear usage context, though it does not address the overlap with siblings like rh_deployer_record / rh_wallet_record that also cover developer and funder records.

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