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

Annotations already declare readOnlyHint / idempotentHint / destructiveHint=false, so the 'Read-only' line is partly redundant, but the description adds material context the annotations cannot: a per-call price of $0.005 USDC via x402, a multi-source fallback chain (Token-2022 -> Metaplex -> Jupiter), and an HTTPS equivalent endpoint. It stops short of describing failure modes for invalid mints.

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 what is returned, followed by safety, price and transport facts in tight succession. The opening sentence is long and packed with commas, but no clause 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?

With no output schema, the description carries the burden of describing the return payload and does so by enumerating the metadata fields and the fallback sources. What remains unstated is behavior on an invalid or non-existent mint and whether market fields are omitted or null when include_market is false.

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%, so both parameters are already documented, including include_market's Jupiter payload. The description adds only a hint that name/symbol resolution can fall back to Jupiter even without that flag, which is a marginal clarification rather than new semantics. Baseline 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?

Names the exact resource (Solana SPL / Token-2022 mint metadata) and enumerates the returned fields: decimals, supply, authorities, extensions, name/symbol/uri. It is clearly distinct from siblings like sol_balance, solana_tx, sol_token_risk and nft_metadata without needing those to be named.

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 implies when it applies (you have a mint address and want token metadata) and notes a Jupiter fallback plus an HTTPS alternative endpoint, but it never states when NOT to use it or points to sol_token_risk / nft_metadata for adjacent needs. Usage is inferred rather than guided.

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