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

With no annotations provided, the description carries the full burden. It discloses this is a read-style check, mentions rate limiting and implied API key requirement beyond 3 calls. It does not explicitly state side effects or idempotency, but the nature of the operation suggests no destructive behavior.

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?

Three sentences with zero waste: first lists outputs, second gives usage context, third provides rate limit info. Front-loaded with the main action 'Returns', making the purpose immediately clear.

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 no output schema, the description should fully explain return values. It lists components (safety score, clusters, authority, etc.) but does not specify their structure (e.g., data types, nesting, JSON shape). Missing error handling or response format details that an agent would need to parse results reliably.

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% for the single 'mint' parameter. The description adds minimal value by restating 'single Solana token mint', but provides no additional syntax, validation rules, or example formats beyond what the schema already includes.

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 safety score, insider clusters, authority status, holder concentration, and live market data for a single Solana token mint. This distinguishes it from sibling tools like check_token_risk_batch (batch) and get_token_risk_history (historical data).

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?

Explicitly says 'Use before recommending or executing a trade on any Solana token', providing clear when-to-use context. Also notes rate limits (first 3 calls free). However, it does not explicitly mention when to avoid this tool (e.g., if batch or history is needed) or provide alternative tool references.

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