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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description usefully adds that data comes from the mempool.space public API and that it is free, which are relevant operational details, though it does not disclose rate limits, freshness guarantees, or failure modes.

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 compact and front-loaded: it immediately names the delivered metrics, then the data source and pricing. Every sentence adds information, and there is no filler, repetition, or unnecessary detail.

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 zero-parameter, read-only status tool, the description gives the essential invocation context: what metrics are returned and where they come from. It does not specify exact units or output format, but that is not critical for correctly selecting and invoking the tool.

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?

The tool has zero parameters and the schema explicitly reflects that by declaring no properties. The description does not need to explain parameter semantics, and none are hidden or undocumented, so the baseline of 4 applies.

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 lists the exact data returned (fee rates, mempool size, block height, next difficulty adjustment, hashrate), making the tool's purpose unmistakable. The 'Bitcoin right now' framing plus the title 'Bitcoin network status' clearly identifies this as a current network status fetcher, distinct from price, fear/greed, or other crypto siblings.

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?

There is no explicit guidance about when to choose this tool over alternatives. It does not mention when not to use it, nor does it route an agent to a sibling for historical data, price data, or other related needs.

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