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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description adds real behavioral context beyond them: that depth='quick_scan' means an unlogged token with contract and holders only and no entry/peak, and that the fomo field reports 24h counts, recent large trades only with no sizes, and the first buy plus still-in traders.

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 primary purpose is front-loaded, but the body is a dense, jargon-heavy run-on that mixes return contents, reading advice, a phantom parameter, and field semantics without clear structure. Several clauses could be trimmed or separated.

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 appropriately takes on explaining return fields (meta.verdict, fomo). But the phantom depth parameter leaves the actual callable signature ambiguous, and no guidance links this tool to the many siblings an agent must choose between.

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 mint parameter is undocumented in the schema, but the description supplies its format (base58). However, it references depth='quick_scan' as if it were a parameter, and no such parameter exists in the input schema, which risks misleading the agent about the call signature.

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?

States a specific verb+resource (fetch any Solana token by mint) and enumerates the returned evidence: holders, bundled-launch read, deployer holdings, socials, and meta.verdict. It is clear what the tool does, though it does not explicitly differentiate from siblings like sol_early_wallets or rh_token_safety.

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?

'Start from the verdict; the rest is evidence' and 'a clean read is not a reason to buy' are interpretation advice, not selection guidance. No when-to-use conditions, prerequisites, or named alternatives versus the many sibling tools are given.

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