get_token_price

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

Without annotations, the description carries the burden; it discloses the 404 condition, which is a non-obvious failure mode. It doesn't mention any side effects or output structure beyond the price/mcap summary, but for a simple lookup this is adequate.

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?

Two sentences with all essential information: output, use case, and error semantics. No redundancy.

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?

The tool is simple (1 param, no output schema, no annotations), and the description covers purpose, selection, and error handling. It clearly states the key data returned (USD price, SOL price, market cap) and the 404 edge case.

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 already fully documents the only parameter ('Base58 mint address'), so coverage is 100%. The description adds no additional meaning beyond the singular 'one mint' context, which slightly reinforces cardinality.

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 names a specific resource ('one mint') and the exact outputs ('USD + SOL price and market cap'). It also gives a concrete use case ('what's X worth now'), which distinguishes it from sibling list tools like get_token_prices.

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?

It explicitly provides a use case ('what's X worth now') and error context (404 = no live price). It doesn't name sibling alternatives, but the singular 'one mint' contrasts with the plural get_token_prices, giving implied selection criteria.

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