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

With no annotations, the description carries the full burden and does substantial work: it discloses the data source ('chain state'), the return contents, and the payment/auth model ('Costs 0.005 USDC (x402, Solana or Base)'). It omits rate limits, latency, idempotency, and failure behavior, which is a real but moderate gap for a read-style check.

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?

Front-loaded with the usage trigger, then outputs, then cost, in a single dense passage with no filler. Every clause carries distinct information an agent needs.

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, so the description must stand alone; it covers when to call, what is returned, and the payment requirement. The remaining gap is the parameter format for the required 'address' field and any 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?

Only one parameter at 0% schema coverage, and its name ('address') is ambiguous. The phrases 'Solana mint' and 'from chain state' weakly imply it expects a mint address rather than a wallet, but no format, encoding, or example is given. The description only partially compensates for the missing schema documentation.

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 ('full rug check from chain state' on a Solana mint) and enumerates the concrete outputs (verdict, risk score, flags, authorities, holders, creator). It does not differentiate itself from siblings solana_token_verdict or solana_token_batch, so an agent cannot tell from the description alone which of the three 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 trigger context: 'Use before any Jupiter or pump.fun trade on an unknown Solana mint.' The 'unknown mint' qualifier implies scoping versus known-good tokens. However, it never names the sibling alternatives (batch, verdict) or states when-not to use it, so routing remains partly inferential.

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