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

Annotations already cover safety (readOnlyHint, openWorldHint), but the description adds material behavioral context they cannot: this is a paid call at $0.030, settled via x402 in USDC on Base or Solana, which affects pre-call planning and explains the `tx` payment path. It also enumerates the returned data fields in place of a missing output schema. It does not cover failure behavior for an unknown mint or partial results.

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 sentences, zero filler: the first front-loads the value proposition and contents, the second carries the pricing/payment term. Every clause earns its place and nothing is repeated between description and title.

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 compensates by listing the returned fields, and it discloses the payment model needed to invoke it successfully. For a 2-parameter read tool the coverage is nearly complete; only error/edge-case behavior for an invalid or non-Solana mint is unaddressed.

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%, and both parameters (mint, tx) are described in the schema, including the regex pattern and the note that tx is an alternative to the X-Payment-Tx header. The description adds no further meaning to the parameters themselves, so the baseline 3 applies.

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+resource+scope: 'Full Solana token report in one call: risk + price + liquidity', and enumerates exactly what is included (rug flags, mint/freeze authority, holders, USD price, deepest pool, liquidity, volume, FDV). It also distinguishes itself from the underlying /token/risk and /token/price endpoints, so an agent can tell it apart from the token_risk and token_price siblings.

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?

'in one call' and 'Everything /token/risk and /token/price return' clearly position this as the consolidated alternative to the two sibling tools, giving an agent the selection rationale. It stops short of explicit when-not guidance (e.g. 'use token_price alone if you only need price and want to avoid the higher fee'), which keeps it from a 5.

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