Bitcoin-MCP-Server

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the tool returns 'comprehensive metrics in string format' and provides a 'macro view of mining centralization and competition.' It details the specific statistics included (e.g., global statistics, network dominance analysis, power distribution insights), which helps the agent understand what to expect. However, it doesn't mention potential limitations like data freshness or rate limits, leaving some gaps.

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, starting with the core purpose. It uses bullet points to organize output details efficiently and ends with clear use cases. While slightly verbose, every sentence adds value (e.g., explaining the macro view and use cases), and there is no redundant information.

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 (macro analysis with multiple metrics), no annotations, 0 parameters, and an output schema, the description is highly complete. It thoroughly explains the tool's purpose, usage guidelines, behavioral output, and specific metrics returned, providing all necessary context for the agent to understand and invoke the tool correctly without relying on structured fields.

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 no parameter documentation is needed. The description appropriately focuses on output semantics by detailing the returned metrics (e.g., total active pools, leader dominance, centralization indicators), which adds value beyond the structured output schema. This compensates well for the lack of parameters.

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 explicitly states the tool's purpose: 'get aggregate statistics and analysis of the Bitcoin mining pool ecosystem.' It specifies the verb ('get') and resource ('aggregate statistics and analysis of the Bitcoin mining pool ecosystem'), and clearly distinguishes it from sibling tools like 'get_mining_pool_by_slug' or 'get_top_10_mining_pools_rank' by focusing on macro-level ecosystem analysis rather than individual pool details.

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 guidance with 'Use cases: When you need to understand the overall mining landscape, assess centralization risk, or compare the gap between dominant and small pools.' This clearly indicates when to use this tool versus alternatives like sibling tools that focus on specific pools or blocks, helping the agent select the appropriate tool for macro-level analysis.

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