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

Annotations already establish safe, read-only, idempotent, closed-world behavior, so the description's job is to add beyond that — and it does: data comes from public on-chain sources only, it is explicitly not financial advice and not a finding about any person, and it discloses tiering (free headline score vs. full breakdown with API key or $0.10 USDC via x402). It omits latency, rate limits, and failure behavior for unknown wallets.

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 scope is front-loaded correctly, but the body is one long run-on sentence stacking many indicator clauses. Every clause is informative, yet the lack of structure (bullets or a shortened list) makes a dense definition harder to scan than it needs to be.

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 carries the burden of explaining what is returned, and it does so by enumerating both the free headline output (score 0-100, band, counts) and the paid breakdown, plus the endpoint. That is close to complete for a one-parameter lookup; only return-shape details for the paid tier and error behavior are missing.

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?

The single `wallet` parameter is fully documented in the schema (base58 Solana or EVM 0x), and schema description coverage is 100%. The description repeats the chain-format detail but adds no new constraint, 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?

Opens with a specific verb-and-resource framing: reputation indicators for a token creator wallet, then enumerates the exact indicators (launch count, bundling share, creator-dump share, liquidity removal, linked wallets). An agent knows what it gets. It stops short of naming the sibling it competes with (token_manipulation_score, kol_scorecard, trace_wallet), so differentiation is left implicit.

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 description makes the use case implied (screening a creator wallet's launch history) and explains the free vs. paid access path, but it never states when to choose this over token_manipulation_score, kol_scorecard, or trace_wallet, which all overlap on wallet and manipulation analysis. Usage is inferable, not directed.

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