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 of behavioral disclosure. It effectively describes the tool's behavior by specifying the return format ('string format'), listing all metrics (block height, hash, timestamp, etc.), and including aggregate statistics. However, it doesn't mention potential limitations like rate limits, error conditions, or data freshness, leaving some behavioral aspects uncovered.

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 with the core purpose, followed by detailed return metrics and use cases. Every sentence adds value: the first states what it does, the second details returns, and the third provides usage guidance. There's no redundant or wasted text.

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 (returns detailed metrics for 10 blocks plus aggregates), no annotations, and an output schema exists (so return values needn't be fully explained), the description is complete enough. It covers purpose, specific outputs, and usage contexts, providing all necessary information for an agent to understand and invoke the tool effectively.

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 schema already fully documents that no inputs are required. The description appropriately doesn't add parameter information, which is correct for a parameterless tool. It earns a 4 (not 5) because it doesn't explicitly state 'no parameters needed,' though this is implied by the context.

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 detailed information and statistics') and resource ('10 most recently mined Bitcoin blocks'), distinguishing it from siblings like get_summary_of_latest_block (single block) or get_bitcoin_network_overview (broader metrics). It explicitly lists the comprehensive metrics returned, making the purpose unambiguous.

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 provides use cases ('analyze recent blockchain activity trends, compare mining pool performance, monitor network congestion'), which clearly indicates when to use this tool versus alternatives like get_bitcoin_network_health or get_summary_of_latest_block. This gives the agent specific guidance on appropriate contexts.

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