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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context beyond the schema: the per-call price ('Costs $0.002 USDC per call (x402)'), which is critical for an agent deciding whether to invoke a paid endpoint. It does not disclose error behavior or caching, but the cost disclosure is the main thing missing from structured fields.

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?

One front-loaded sentence names the resource first, then lists the returned fields and closes with the cost. Every clause earns its place: the field enumeration substitutes for the absent output schema and the price note drives invocation decisions.

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 must describe the return payload, and it does so thoroughly (name, symbol, image, supply, decimals, price, market cap, authorities, royalties, creators). Combined with the cost note and a single fully-documented parameter, an agent has nearly everything needed. The only gap is disambiguation from sibling token/NFT tools.

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 'id' parameter is documented as 'Mint or asset address'. The description loosely reinforces that the id can be either a mint or an NFT asset, but adds no format, prefix, or validation guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states the resource precisely (any Solana token mint or NFT) and enumerates the exact metadata returned, including authority, supply and price fields. That is far more specific than the bare title, but it never distinguishes this tool from adjacent siblings such as solana_nfts, token_solana or nft, so an agent must guess which of those 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?

Usage is implied by the phrase 'for any Solana token mint or NFT' and by the inline framing questions ('can more be minted? can accounts be frozen?'), which hint at when this data matters. However, there is no explicit when-to-use, no mention of when NOT to use it (e.g. for transaction history use solana_history, for wallet holdings use solana_wallet), and no alternatives named.

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