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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions real-time updates and data fields (prices, changes, volumes) but omits critical details such as the effect of the 'short' parameter, the exact set of cryptocurrencies covered, and the absence of a symbol selection parameter. This leaves behavior ambiguous.

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 concise at two sentences, but it uses 'live' and 'real-time' redundantly. The key information is front-loaded in the first sentence, making it effective overall.

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 tool with one optional parameter and no output schema, the description covers the main purpose but misses key context about the batch scope and the difference between short and full quotes. The lack of a symbol parameter is unexplained, making the tool's behavior ambiguous.

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 only parameter 'short' with a clear description, so the baseline is 3. The tool description adds no additional parameter context beyond what the schema already provides.

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 that the tool accesses live price data for cryptocurrencies, explicitly mentioning the batch aspect with 'single request.' This distinguishes it from singular quote tools, though it does not name alternatives.

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 batch usage via 'wide range' and 'single request,' but it does not explicitly state when to use this tool versus methods like getCryptocurrencyQuote or getCryptoQuotes. No exclusion or alternative guidance is provided.

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