get_btc_fee_estimates

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

The description prominently labels the tool as 'READ-ONLY', consistent with annotations (readOnlyHint=true). It details the five output labels with block-time estimates and explains the fallback behavior between mempool.space and Esplora endpoints, adding valuable behavioral context beyond the annotations.

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 concise, well-structured, and front-loaded with 'READ-ONLY'. Every sentence adds value: purpose, output details, and source/fallback. No wasted words.

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 zero parameters and no output schema, the description fully explains what the tool returns (five labels with time estimates), the unit (sat/vB), and the data source with fallback. It is complete for the tool's complexity.

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 no parameters (100% coverage), so the baseline is 4. The description adds no parameter information (none needed) but enriches understanding by explaining output labels and data sources.

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 reads current Bitcoin fee-rate recommendations in sat/vB. It lists the five specific labels returned, distinguishing it from other Bitcoin-related tools like get_btc_balance.

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 implicitly indicates use for fee estimation but lacks explicit guidance on when to use it versus alternatives. However, the sibling list contains no other fee-estimate tool, so guidance is adequate but not explicit.

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