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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds material context: a per-call price ($0.002), the payment rail (x402 via USDC on Base or Arbitrum One), the data provenance ('reconstructed from chain event logs'), and a non-advice disclaimer. That payment/auth requirement is exactly the kind of operational fact an agent must know before invoking, and it is not recoverable from the annotations.

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 purpose and the decision it serves are front-loaded in the first clause, followed by input shapes, then return contents, then cost. It is a single dense paragraph rather than a list, and the trailing 'not financial advice' plus the duplicated enumeration of fields push it slightly past what is strictly needed, but essentially every sentence carries information.

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 compensates by naming the return payloads (supply, treasury balance, multiplier, ledger coverage, integrity flags, known look-alikes), and it covers input shapes, chain, cost and payment. For a one-parameter read-only tool, an agent has everything required to decide and to invoke.

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 coverage is 100% and the single parameter already documents the ticker or 0x-address format, so the baseline would be 3. The description earns an extra point by adding that the address must live on Robinhood Chain (chain ID 4663) and by explaining that the two input shapes produce semantically different result types (listed-token report vs. 'which token it imitates').

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 opens with a specific verb and resource plus the decision it supports: 'Check a Robinhood stock token before an agent buys, holds or accepts it', and it names what it resolves (Robinhood-listed contract vs. a known look-alike). It then enumerates the returned fields, which is unusually concrete. It never names a sibling tool outright, so the differentiation from token_snapshot and find_token is inferred from the 'is this legit?' framing rather than stated.

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 when-to-use condition is explicit and situational: before buying, holding or accepting a token. There is no when-not guidance, no statement of what to use instead for price/history (token_events, token_snapshot), and no note about what happens for an unlisted ticker. Clear context, missing exclusions and alternatives.

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