get_btc_fee_estimates

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

Beyond annotations (readOnlyHint, etc.), the description reveals the data source (mempool.space with fallback to Esplora) and the exact labels returned. This provides significant behavioral context that helps the agent understand reliability and fallback behavior.

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?

Three sentences, each adding value: purpose and unit, specific labels, and data source. Front-loaded with 'READ-ONLY' and clear verb. No unnecessary 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 covers what the tool returns (five labels with meaning) and where the data comes from. An agent can confidently use the tool and interpret results.

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?

With zero parameters (schema coverage 100%), the description compensates by thoroughly explaining the output labels and their meanings, which is essential for interpreting results. Baseline for no parameters is 4, and the extra detail on return values and data source elevates it to 5.

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 it provides Bitcoin fee-rate recommendations in sat/vB, lists the five specific labels with their meanings (fastestFee, halfHourFee, etc.), and distinguishes itself from other BTC tools by focusing solely on fee estimates. No sibling tool duplicates this purpose.

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?

While the description does not explicitly state when not to use the tool or name alternatives, it clearly implies its use for obtaining Bitcoin fee recommendations. Given the uniqueness of this tool among siblings, explicit exclusions are not critical.

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