estimate_transaction_cost

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

With no annotations provided, the description carries the full burden. It successfully discloses dual-currency output (sats/USD) and comparative urgency analysis features, but omits methodological details like data sources (mempool-based?), specific urgency tiers (high/medium/low?), or whether estimates are real-time vs cached.

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 in two sentences with zero waste. It front-loads the core functionality (cost estimation in dual currencies) and uses the second sentence for value-add features (savings comparison), making every word earn its place.

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?

For a tool with 3 optional parameters and an output schema (indicated in context), the description adequately covers the core functionality. However, given the complexity of fee estimation and the lack of schema documentation, it should mention that results vary by current network conditions or specify what 'urgency levels' means.

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?

Given 0% schema description coverage, the description partially compensates by enumerating the four supported address types (p2pkh, p2sh-p2wpkh, p2wpkh, p2tr) for the address_type parameter. However, it completely omits semantic explanations for input_count and output_count, leaving two-thirds of the parameters undocumented.

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 estimates Bitcoin transaction costs in both sats and USD at different urgency levels, with specific mention of address type support. It distinguishes itself from simple fee estimators by mentioning 'how much you save by waiting,' though it could more explicitly differentiate from siblings like estimate_smart_fee or get_fee_recommendation.

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 implies usage context through 'different urgency levels' and 'save by waiting,' suggesting when users want cost comparisons across confirmation speeds. However, it lacks explicit guidance on when to use this versus sibling fee estimation tools or prerequisites like needing transaction draft details (input/output counts).

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