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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the data sources, caching window (15-30 s), supported token categories, and per-call payment cost via x402. This adds substantial operational context, though it does not describe failure modes or payment error handling.

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?

The description is front-loaded with the core purpose, followed by source details, supported token types, caching, and cost. Every sentence adds useful information without repetition or filler.

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 lists the relevant returned metrics: price, liquidity, 24h volume, 24h change, FDV, and pool age. It also covers data provenance, caching, and payment cost, which is sufficient for an agent to invoke this simple lookup tool 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?

Schema coverage is 100%, so the mint and tx parameters are already documented in the input schema. The description reinforces that lookup is by mint and mentions x402 payment, but it does not add parameter-specific meaning beyond the schema baseline.

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 clearly states it returns USD price, liquidity, and volume for any Solana token by mint, and names Jupiter and DexScreener as data sources. It is specific about the resource and scope, though it does not explicitly contrast itself with sibling tools such as price, prices, or token_report.

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 usage for Solana token price/liquidity/volume checks and notes it works for new and meme tokens. However, it gives no explicit when-to-use or when-not-to-use guidance versus alternatives like token_report or generic price tools.

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