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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavior beyond them: large trades only, no sizes, the 15-buy scoring threshold, the PumpPill wallet matching, and the critical found=false vs inactive distinction with a data start date. It stops short of 5 only because return shape/pagination is not characterized.

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?

It is a single dense run-on sentence stuffed with semicolon-separated clauses. The purpose is front-loaded, but the operationally critical found=false and large-trades-only caveats are buried at the tail, hurting scannability.

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 must carry the return semantics – and it does, enumerating buys with market cap, sells with realized profit, tokens touched, scored records, and the Robinhood Chain wallet. The found=false/data-start note closes the biggest ambiguity; only paging or volume limits are left open.

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 0% and the single 'handle' property carries no description, so the description must compensate. It does clarify the handle is a FOMO name, but it adds no format, casing, or lookup-failure detail beyond that single phrase.

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 opening sentence states a specific verb+resource: what one FOMO trader did in the last 7 days, keyed by FOMO name. It is clearly distinct from chain-oriented siblings like rh_wallet_record or sol_early_wallets, but it never explicitly names or contrasts an alternative, so it falls short of a 5.

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?

Usage is implied by 'one trader ... by FOMO name' and the found=false note explains how to read absence of data, but there is no explicit when-to-use versus alternatives (e.g., a chain-level wallet record tool). The data start date is helpful context but not routing guidance.

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