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

With no annotations, the description carries the full burden and does well: it discloses error semantics (400 bad input, 422 not-a-mint, 404 unknown, no charge on failures), billing ($0.002 via x402), and the shape of the returned JSON. It does not mention rate limits, caching, or whether failures on the same mint are retried, which keeps it out of the top band.

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 Input, Output, error behavior, example and price — every clause carries information and there is no filler. The list-style output enumeration is dense but scannable.

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 exists, so the description must describe returns, and it does so field-by-field including the Token-2022 extension set. Combined with error codes and pricing, an agent has everything needed to decide and invoke correctly.

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 and schema coverage is 100%, so the schema already covers base58/32-byte format and error codes. The description adds a concrete worked example (`?mint=EPjFWdd5...`) that makes the expected identifier form immediately recognizable, which is a small but real gain over the schema.

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?

Names a specific resource (Solana SPL / Token-2022 mint) and enumerates exactly what it returns: supply, decimals, authorities, extensions, issuer. The 'basics' framing cleanly separates it from the adjacent sol_token_risk sibling without opening either schema.

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?

Opens with an explicit trigger — 'Use when an agent needs a Solana token's basics before quoting, transferring or accepting it' — which gives a concrete decision context. It stops short of naming sol_token_risk as the alternative for risk assessment, so the routing rule is implied rather than stated.

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