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

With no annotations, the description carries the burden and does well: it discloses that the result is read from chain state, the exact output classes, the cost (0.001 USDC via x402) and payment chains (Solana or Base). Missing latency, caching, or failure behavior, but the paid-call requirement is a valuable behavioral disclosure the schema cannot express.

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 dense sentences: the usage condition is front-loaded, then output, then decision rules and cost. No filler; each clause adds actionable information.

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?

No output schema or annotations exist, yet the description covers return values, decision thresholds, and payment cost, which is what an agent needs to call it. It falls short only on the input address semantics and edge/error behavior.

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?

One required parameter ('address') with 0% schema description coverage, and the description never names or explains it. The token-check framing implies it is a token mint address, which is some compensation, but format/expectations are left to inference.

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: a go/no-go rug check that reads chain state and returns a verdict. It clearly conveys what the tool produces (SAFE/CAUTION/DANGER plus score and flags). It does not differentiate itself from the siblings (solana_token_check, solana_token_batch, tokenguard_info), leaving ambiguity about which check flavor to pick.

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?

Gives explicit triggering context ('about to buy or swap into an unknown Solana token') and even decision rules for acting on the result ('Skip DANGER, reduce size on CAUTION'). It stops short of saying when to prefer this over the sibling check/batch tools.

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