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

With no annotations, the description carries the burden and does disclose meaningful traits: the live data source (mempool.space), the exact outputs returned, and the per-call cost ($0.02 USDC, eip155:8453). It does not explicitly declare read-only/no-side-effect status, but the fee-market nature makes it evident, and the pricing disclosure is genuinely useful behavioral context.

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?

Front-loaded with the concrete returned artifacts, then usage, then pricing, in three compact sentences. The line 'No more guessing sats before broadcasting' is mild marketing but costs little; overall it is efficient and well ordered.

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?

No output schema exists, so the description must characterize the response, and it does: fee tiers, backlog, and total tx cost. With only one schema-documented parameter and the payment terms stated, an agent has enough to call it correctly; only the read-only assurance is implicit.

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?

Schema coverage is 100% and the single txSize param is documented there ('Simple transfer ≈ 140 vBytes'). The description reinforces the unit ('in vBytes') but adds no new syntax or format detail beyond the schema, so it sits at the baseline for high-coverage schemas.

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 states a specific verb+resource: live sat/vB fee tiers, mempool backlog, and total fee cost for a given tx size, all qualified as 'Bitcoin' from mempool.space. That scope clearly separates it from the crypto_gas_* siblings, which are Ethereum-oriented, though no sibling is named. Purpose is specific but lacks explicit tool-to-tool contrast.

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?

It gives an explicit trigger: 'Use this when an agent needs to live sat/vB fee tiers + cost for your tx size.' That is clear context for selection, but there are no exclusions and no alternatives named (e.g., when to prefer crypto_gas_price instead).

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