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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely useful non-schema behavior: the cost ($0.01) and the underlying route (GET /x402/btc-fees). It does not restate the 402 payment handshake, which is fine since the schema covers it, but it also omits latency/refresh cadence for a time-sensitive fee forecast.

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?

One compact sentence plus a route/price fragment; the return payload is front-loaded and every token carries information. No filler or restatement of the title.

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?

With no output schema, the description usefully enumerates the four returned horizons so the agent knows what it gets back, and it discloses price and endpoint. Only the paid-call flow (first call returns a 402 challenge) is left entirely to the schema description.

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 description coverage is 100% and the single `payment` parameter is fully documented there, so baseline is 3. The description's 'No params' is a slight mismatch with the schema — accurate for functional inputs but it could confuse an agent into never supplying the payment proof on a retry.

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?

States a specific resource (Bitcoin sat/vB fee forecast) and enumerates the exact horizons returned: next block, 30 min, 1 hour, economy. An agent can tell this is a fee-estimate tool rather than a price tool, though no sibling (e.g. get_gas_price, get_crypto_prices) is named to sharpen the boundary.

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?

Usage is only implied by the resource name and the 'No params' note — the agent can infer you call it when you need BTC fee rates. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as get_gas_price for other chains.

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