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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds meaningful context beyond that — that the call is single-pass, that power flags are read 'in the implementation behind a proxy', and that part of the payload (price, liquidity, market cap) comes from an external DexScreener source. It stops short of describing failure modes for non-ERC-20 or non-contract 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 use case and the 'one call, decoded' value proposition before the return-value enumeration, which is dense but every listed item is genuine payload. It is a single long sentence, readable but slightly list-heavy rather than structured.

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?

There is no output schema, so the description correctly carries the full burden of describing return values, and it does so thoroughly across metadata, ownership, proxy implementation, code powers and market data. Minor gaps remain around edge cases (non-token contracts, renounced-owner representation) that an agent might want spelled out.

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 100%, so both parameters (address, quote) are already fully documented in the schema, including the quote flag's dry-run semantics. The description never touches parameter behavior, so the baseline of 3 applies with no added value.

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 states a specific verb+resource — 'know what a Robinhood Chain contract is... one call, decoded' — and enumerates the exact data returned (ERC-20 metadata, owner, EIP-1967 implementation, exposed powers, DexScreener market data). The chain-specific framing partially separates it from generic siblings like scan_token or token_verdict, but it never explicitly disambiguates from those.

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?

'Use this when you need to know what a Robinhood Chain contract is before touching it' is a recognizable use-case trigger and implies a pre-interaction audit context. However, it offers no when-not guidance and never routes the agent away from the obviously overlapping siblings (scan_token, token_verdict), leaving the choice to inference.

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