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

With no annotations, the description adds meaningful context: it discloses a pay-per-call cost ($0.005 USDC) and enumerates what the response contains. It doesn't cover permissions, rate limits, or failure modes, but the pricing and output disclosure is substantive beyond any structured field.

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?

Two tightly packed sentences: purpose first, output enumeration second, cost third. Zero filler, front-loaded, and every clause 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?

For a read-only informational tool with no output schema, the description enumerates the key return fields and discloses cost, which is sufficient to call it correctly. It stops short of describing the risk-score scale or the exact response shape, but the core is covered.

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 parameter exists and schema coverage is 100%, so the schema already documents the base58 mint address. The description adds no format or validation detail beyond the schema, which is the expected baseline for a fully-documented single parameter.

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 and resource ('Check if a Solana token is safe to trade') and enumerates the checks it performs (rug pull, honeypot, freeze/mint authority, insider networks, transfer fees, risk score). Clear purpose, though it does not explicitly distinguish itself from sibling token_risk_score.

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?

Usage is only implied by 'safe to trade' and the return fields; there is no explicit when-to-use versus alternatives like token_risk_score, token_holders, or token_metadata, and no exclusions or prerequisites beyond the single required input.

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