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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds real substance: the envelope's live block fields (last_mint_live, launched_live, bonded_live, mints_since_asof, ticker_asof), the KOL tagging payload, and the not_token response for dev wallets. It stops short of stating rate limits, caching, or failure modes for malformed 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?

The opening two sentences ('What the KOL wallet launched, and how it ended. Rugged of resolved, seconds to the pull, every count with its N.') are cryptic marketing fragments that consume prime front-loaded space before the actual purpose appears mid-paragraph. The later content is informative but dense and unordered, so the agent must parse past noise to find the operative statement.

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 carries the burden of explaining returns, and it does so thoroughly: outcome label, liquidity/market-cap, holder counts, launch counts, the envelope's live block, and the not_token variant. Coverage of error paths and field-level semantics of the numeric counts is thinner than ideal, but an agent has enough to call and interpret it.

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?

With one parameter at 100% schema coverage, the schema already documents the address and supplies a worked example. The description restates the accepted formats (Solana mint / 0x contract) without adding syntax, validation, or normalization detail beyond what the schema provides, so the baseline 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 sentence 'Look up one token and return what GROUNDTRUTH counted about it' gives a specific verb and resource, and the enumeration of outcomes (rugged, died, graduated, survived) pins the domain. It also implicitly separates itself from wallet-oriented siblings by stating that a dev WALLET paste returns not_token plus a creator_record. However, it never names or contrasts an actual sibling tool, so the differentiation is indirect.

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 clarifies accepted inputs (Solana mint or Robinhood Chain 0x address) and the fallback behavior when a dev wallet is passed, which is genuinely useful routing guidance. But it gives no guidance on when to prefer this over groundtruth_screen_creator, groundtruth_creator_replay, or groundtruth_wallet_record, leaving the sibling-selection decision to inference.

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