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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral context: the fallback source chain (Binance→Coinbase→Kraken), the aggregate volume/market cap via CoinLore, the cache TTL of 15s, and the lack of auth requirement. This goes well beyond annotations without contradicting them.

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 core purpose, and packs in crucial operational details (source, TTL, auth) without verbose filler. Every clause earns its place.

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 no-parameter, read-only tool with no output schema, this description is remarkably complete. It states the return fields (price, 24h change, high, low, volume, market cap), the source fallback, cache TTL, and the absence of auth. An agent can invoke it correctly with zero additional context.

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?

There are zero parameters, so the schema is trivially 100% covered. The description doesn't need to explain parameters, but it does imply the API requires nothing. Since there is no parameter semantics to decode, a 4 is appropriate as the baseline for zero params.

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 action ('Fetches'), resource ('current Bitcoin price in USD'), and includes the key fields (24h change, high, low, volume). This distinguishes it from siblings like 'tf_crypto_movers' which likely covers multiple cryptocurrencies. The source chain and use case add further specificity.

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?

Explicitly states when to use: 'for crypto trading decisions or when the agent needs a fresh BTC quote.' This gives clear context and a trigger situation. It does not explicitly name alternatives or state when not to use, but with such a clear resource, the when-to-use is adequate.

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