get_btc_price

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

No annotations provided, so description carries full disclosure burden. Successfully documents auth requirements ('free, no API key'), data source ('CoinGecko'), and return schema ('price, 24h change, and market cap'). Minor gap on rate limits or caching behavior.

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?

Three sentences with zero waste: sentence 1 establishes source and auth, sentence 2 previews return values, sentence 3 provides usage context. Front-loaded with critical operational details (CoinGecko, no API key).

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?

Appropriate for low-complexity tool with 0 parameters and existing output schema. Covers data provenance, authentication, return value summary, and integration with sibling workflows (fee conversion). No significant gaps given the tool's narrow scope.

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?

Input schema has 0 parameters, establishing baseline 4. Description correctly omits parameter discussion as none exist, matching the empty schema without contradiction or confusion.

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?

Specific verb 'Get' with clear resource 'BTC/USD price' and explicit data source 'CoinGecko'. Distinct from technical blockchain analysis siblings (analyze_block, get_mempool_info, etc.) by focusing on market data rather than on-chain data.

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?

Provides concrete use case 'convert sat/vB fees into dollar amounts' which contextualizes the tool within the server's Bitcoin fee analysis domain. Lacks explicit 'when not to use' or comparison to sibling get_market_sentiment, but clear positive guidance is present.

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