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

Annotations only declare read-only/open-world; the description adds operationally important behavior an agent cannot get from them: an exact price ($0.002 USDC per successful call), the payment rails (x402 on Base, Solana or Arc), and that failed calls are not charged. The stated upstream (public Solana RPC) also tells the agent how authoritative the result is.

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?

A single tight paragraph, front-loaded with the substantive checks and the scope exclusion before the pricing tail. Dense but every sentence contributes; it could be marginally easier to scan if the not-checked caveat were its own clause, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description covers source, cost, and scope limits for a single-parameter tool. Minor gaps remain around Token-2022 mints and network selection for payment, but nothing that would cause an incorrect invocation.

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 with 100% schema description coverage (base58, 32-44 chars), so the schema carries the semantics. The description adds no address format, Token-2022 vs classic SPL distinction, or failure behavior for an invalid mint, so this is the baseline rather than above it.

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?

A specific verb+resource ("Solana SPL token mint audit") followed by the exact facts it returns: mint authority revoked, freeze authority revoked, supply, decimals. It also carves out an adjacent check it does NOT perform (metadata immutability), which separates it from broader safety tools like token_composite_safety_score or liquidity_lock_inspector in the sibling list.

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?

The data source is stated ("from the public Solana RPC") and a clear exclusion is given (metadata immutability is not checked), so an agent knows the boundary of the answer. It stops short of naming which sibling to call when the agent actually needs the metadata-immutability or composite-risk answer, so routing is left to inference.

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