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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful behavioral context beyond annotations: the $0.001 USDC cost per call and the byte-identical relationship to the GET endpoint, which sets response expectations.

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 short sentences deliver the data output, pricing, and endpoint equivalence with no filler. The most important information (what the tool returns) is front-loaded. The trailing '?' is a minor typo but does not hurt usefulness.

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 parameterless, read-only tool with annotations and an output schema already provided, the description covers everything an agent needs to select and invoke it: output semantics, cost, and exact endpoint contract. Nothing meaningful is missing.

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?

There are zero parameters and the schema description coverage is 100%, so there is no parameter documentation burden on the description. The description still adds value by naming the returned fee categories, which helps the agent interpret the output.

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 identifies the resource as Bitcoin fee estimates and enumerates the exact fee targets returned (fastest, half-hour, one-hour, economy, minimum), which makes the tool's purpose obvious. It lacks an explicit verb like 'returns' and does not name sibling tools, but the endpoint reference and fee-target list are enough to set it apart from related market_btc_* tools.

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 cost and endpoint identity are useful operational prerequisites, and the description implies this is the tool for Bitcoin fee estimates. However, it gives no explicit guidance on when to choose this over sibling tools such as market_btc_spot_prices or chain_fee_data, nor any when-not-to-use conditions.

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