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

Annotations already cover readOnly, idempotent, open-world and non-destructive semantics, so the bar is lower. The description adds genuinely non-structured context: the 0.01 USDC cost, the settlement endpoint, the payTo address, and the 402-then-retry flow with PAYMENT-SIGNATURE or X-PAYMENT. That is real behavioral disclosure beyond the annotations, though it omits whether the charge is per-call or on retries.

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?

Purpose is front-loaded in the first clause, followed by the payment details an agent needs before invoking. It is dense but every sentence carries information; the endpoint URL and payTo address are necessarily verbose but useful.

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 naming the returned fields (supply, decimals, mint authority, freeze authority) and by spelling out the payment handshake required to actually get a response. The only gap is the absence of any tie-break against the similar sibling tool.

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 description coverage is 100% and the single parameter already documents itself as a base58 Solana SPL mint address with a regex pattern. The description adds no syntax or format meaning beyond that, so the baseline of 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 (on-chain facts for a Solana SPL mint) and enumerates the returned facts (supply, decimals, mint authority, freeze authority), so an agent knows exactly what it gets. It does not, however, differentiate itself from the sibling sol_token_brief, which sounds like an overlapping resource.

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 description explains the payment mechanics but gives no guidance on when to choose this tool over sol_token_brief or any other sibling. There is no when-to-use or when-not-to-use statement; the agent must infer the selection criteria.

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