Bitcoin-MCP-Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the tool returns 'detailed metrics in string format for each of the 10 leading mining pools' and lists specific metrics (rank, name, hashrate, network share). It also explains the data's purpose ('historical performance and consistency... more stable view than current block count alone'), adding valuable context beyond basic functionality.

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 well-structured and front-loaded: the first sentence states the core purpose, followed by output details, data significance, and use cases. Every sentence adds value, with no wasted words, making it efficient and easy to parse.

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?

Given the tool's complexity (historical data analysis), no annotations, and an output schema present, the description is complete. It explains what the tool does, what it returns, why the data is useful, and when to use it, covering all necessary aspects without needing to detail return values explicitly.

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 input schema has 0 parameters with 100% coverage, so the baseline is 4. The description appropriately does not discuss parameters, focusing instead on output semantics and usage context, which adds value without redundancy.

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's purpose: 'get the top 10 Bitcoin mining pools ranked by their average hashrate over the last 3 months.' It specifies the verb ('get'), resource ('top 10 Bitcoin mining pools'), and timeframe ('last 3 months'), distinguishing it from siblings like 'get_top_10_mining_pools_rank' which lacks the hashrate and timeframe 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?

The description provides explicit usage context with 'Use cases: When you need to analyze mining pool trends over time, understand hashrate distribution patterns, or identify consistently dominant pools.' It distinguishes from tools like 'get_top1_mining_pool' by focusing on top 10 over 3 months, but does not explicitly state when not to use it or name alternatives.

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