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

With no annotations provided, the description carries the full burden. It appropriately indicates a read-only, real-time data operation and lists high-level output categories. However, it omits details such as response structure, rate limits, or how 'short' differs from the full quote endpoint, leaving behavioral expectations partially unspecified.

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 two sentences, front-loaded with the action and resource, and contains no redundant or irrelevant content. Every clause adds useful information about the API and the returned data.

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?

In the absence of an output schema, the description does provide a high-level summary of return values (prices, changes, volume). But it lacks specifics about the exact fields, the meaning of 'short' relative to full quotes, or any formatting details, making it adequate but not comprehensive.

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 fully documents the single parameter with an example (BTCUSD), so the description doesn't need to add much. It adds no new semantic detail beyond the schema, and the baseline of 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?

The description clearly states the tool accesses real-time cryptocurrency quotes and returns a concise overview of prices, changes, and volume. However, it doesn't explicitly distinguish it from sibling tools like getCryptocurrencyQuote or getCryptoQuotes, so it's not a 5.

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 phrase 'concise overview' implies a quick snapshot use case, but the description does not provide explicit when-to-use guidance or name alternatives for more detailed or batch quotes. Usage context is only implied.

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