get_btc_mempool_info

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

No annotations are provided, so the description bears the burden. Its wording implies a harmless read-only stats call, but it never explicitly says it has no side effects, requires no authentication, or discloses rate limits or freshness/staleness of the mempool snapshot.

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 first two sentences are well front-loaded and earn their place. The appended tip promoting earning_opportunities is unrelated to selecting or invoking this tool and adds noise to an otherwise tight definition.

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, no parameters, and no annotations, the description does the needed work by naming the metrics returned. The only gaps are the absent behavioral notes (read-only nature, data freshness) that nothing else in the definition supplies.

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 takes zero parameters, so the baseline is 4. There is nothing parameter-related for the description to compensate for, and it correctly omits any parameter discussion.

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 verb+resource ('Get current Bitcoin mempool statistics') and enumerates the returned fields (transaction count, virtual size, total fees, fee histogram). It is clear what the tool does, but it never distinguishes itself from close siblings such as get_btc_fees, get_mempool_info, or get_network_status.

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 through the stated purpose ('monitoring network congestion and estimating confirmation times'), which suggests a legitimate scenario but gives no explicit when-to-use vs. when-to-use-a-sibling guidance. The trailing tip about earning_opportunities is a cross-sell, not usage guidance for this tool.

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