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

With no annotations, the description carries the full behavioral burden. It usefully discloses the data source, freshness intent, and lookup flexibility, but it does not mention return currency/units, rate limits, error behavior, or output shape. This is adequate for a simple getter but not richly transparent.

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?

A single, well-structured sentence delivers the key facts with no filler. The verb, resource, source, and query modes are all front-loaded, making it easy for an agent to parse quickly.

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?

For a one-parameter tool this is reasonably complete, but the absence of an output schema and annotations means the description should cover return format, currency, or error cases. It captures the core intent but leaves an agent guessing about the actual response shape and edge behavior.

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?

The schema provides only a bare 'query' string with 0% description coverage, so the description rightly steps in by explaining that the query can be an id, symbol, or contract address. However, it does not clarify how those identifiers are disambiguated, case sensitivity, or expected formatting, leaving some ambiguity.

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 a specific verb ('Get'), a clear resource ('current token price'), and a specific source ('CoinGecko'), plus the three accepted query modes. This clearly differentiates it from the sibling analysis/checking tools without needing to open the schema.

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?

Use is implied: call this when you need a current token price from CoinGecko. However, the description does not explicitly say when to prefer this tool over sibling tools or mention any exclusions, so the guidance is implicit rather than explicit.

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