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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety profile is covered. The description adds real value beyond them: it discloses the pricing model ('0.030 USDC per call, included in subscriptions') and the analytical basis (snapshot history). It omits rate limits and any freshness/latency notes.

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?

Front-loaded with the use case and then the capability list, which is efficient. The comparative sentence about RugCheck is slightly promotional, but it still earns its place as differentiation; overall it is a single dense pass with little waste.

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 return-value burden and does describe the deliverable (graph findings, concentration, dynamics, blacklist proximity, verdict). Combined with full annotation coverage of the read-only/idempotent profile, an agent has enough to invoke it correctly, though latency/rate context is absent.

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?

Only one required parameter (mint) with 100% schema description coverage, so the schema fully documents the input. The description adds no format or validation guidance for the mint beyond what the schema pattern provides, making the baseline 3 appropriate.

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?

Names a specific verb and resource ('see who really holds it' for a Solana token) and enumerates the concrete outputs: shared-funding linkage among top holders, merged-wallet concentration, holder/liquidity dynamics, blacklist proximity, and a verdict. This clearly separates it from siblings like token_holders_delta or market_snapshot.

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?

States explicit context for use: 'before buying or holding a Solana token'. It also positions itself against a known alternative ('Goes deeper than a single safety score such as RugCheck's'), though it does not name any sibling tool or state when NOT to use it.

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