Bitcoin-MCP-Server

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

With no annotations provided, the description carries full burden and does well by disclosing: the tool returns detailed metrics in string format, specifies exactly what metrics are included (rank, blocks mined, percentage, grand total), and explains the ranking's significance ('current distribution of Bitcoin mining power'). It doesn't mention rate limits or data freshness, but covers core behavior adequately.

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 efficiently structured: first sentence states purpose, second details return format, third explains significance, fourth lists use cases. Every sentence adds value with zero redundant information, and it's appropriately sized for a no-parameter tool with rich output.

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 0 parameters, no annotations, but an output schema exists, the description provides excellent context: it explains what the tool does, what metrics it returns, why the ranking matters, and when to use it. The output schema will handle return structure details, so the description focuses on semantic understanding.

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 doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and output.

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 specific action ('get the ranking of the top 10 Bitcoin mining pools') and resource ('based on the number of blocks mined'), distinguishing it from siblings like 'get_mining_pool_by_slug' (single pool) and 'get_mining_pools_hashrates_3month' (different metric/timeframe). It avoids tautology by explaining the ranking methodology.

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 explicitly lists use cases ('understand mining centralization, identify the dominant mining pools, or analyze the distribution of network hashrate'), providing clear context for when to use this tool. It implicitly distinguishes from siblings by focusing on top-10 ranking rather than individual pools or historical data.

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