Check Solana token risk

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

With no annotations provided, the description carries the burden. It goes beyond a basic list by explaining what 'insider wallet clusters' means (wallets sharing a first funder), and specifies all output components. However, it does not discuss potential limitations or data availability, but the disclosed methodology adds valuable behavioral context.

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 description is two sentences with no wasted words. The first sentence front-loads the core output, and the second gives a concise usage directive. Every word earns its place.

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?

Given the tool has only one parameter and no output schema, the description adequately covers what the tool returns (score, clusters, authority, concentration, price/liquidity/volume) and when to use it. It is sufficiently complete for an agent to decide and invoke correctly.

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 100% with the single 'mint' parameter having a clear description. The tool description also reiterates 'single Solana token mint,' but adds minimal extra semantics beyond the schema. Baseline 3 is 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?

The description clearly states the tool returns a 0-100 safety score and specific on-chain metrics for a single Solana token mint. The verb 'Returns' combined with the explicit resource ('single Solana token mint') distinguishes it from batch and history sibling tools.

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 explicitly states when to use the tool: 'Use before recommending or executing a trade on any Solana token.' It provides clear context but does not explicitly mention alternatives or exclusions, though the 'single' constraint implicitly differentiates from the batch tool.

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