get_crypto_price

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety and idempotency profile. The description adds no further behavioral context such as data freshness/latency or rate limits, so it does not go meaningfully beyond the annotations.

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?

Purpose is front-loaded in the first sentence, followed by cleanly separated Args and Returns sections. The Returns block is mildly redundant given an output schema exists, but nothing is bloated.

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 simple one-parameter query tool with a full output schema and rich annotations, the definition covers what an agent needs. The only minor gap is the absence of any note on quote freshness or rate behavior, which is not critical for calling it 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 0% for the single 'symbol' param, so the description carries the burden — and it does so well by giving concrete accepted formats ('BTC', 'ETH', 'bitcoin', 'ethereum', 'BTC-USD'). This clarifies that tickers, names, and pair strings are all valid, which the bare schema does not.

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?

States a specific verb+resource: 'Get cryptocurrency price and market data.' The resource ('cryptocurrency') cleanly distinguishes it from siblings like get_stock_price, get_commodity_price, and get_forex_rate, though it never names those alternatives explicitly.

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?

Usage is implied by the resource scope — an agent will infer this is the tool for crypto quotes — but there is no explicit when-to-use guidance and no exclusions against the many adjacent price tools (get_stock_price, get_commodity_price).

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