get_mempool_snapshot

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

With no annotations, the description carries the full burden. It transparently discloses that the tool is free and requires no wallet, which is important for an agent assessing access requirements. It also specifies that it returns current data and lists the components, giving a clear picture of what the agent receives. It does not mention rate limits or refresh latency, but for a simple read-only snapshot this is acceptable.

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 two sentences, front-loaded with the resource name and immediate list of return fields. The 'FREE — no wallet needed' adds useful context without fluff. Every word earns its place, making it exceptionally concise and well-structured.

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?

Given the tool's simplicity (no parameters, no output schema), the description adequately conveys what the tool returns and its access requirements. It covers the essential return content (count, vsize, fee info, histogram) and the auth/cost context. There is no missing information that would prevent an agent from invoking it correctly.

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 coverage is 100% (vacuously), so there is no parameter ambiguity to resolve. The description adds no parameter-specific details because there are none; per the rubric, the baseline is 4 for a zero-parameter tool.

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 specifies the resource (current Bitcoin mempool) and enumerates exactly what data is returned: transaction count, total vsize, min/relay fee, and fee-rate histogram. This is a specific verb+resource structure that distinguishes it from sibling tools like get_network_snapshot or get_current_fees.

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 description implies usage for anyone needing a snapshot of current mempool metrics, and the 'FREE — no wallet needed' note suggests it is a public, low-friction endpoint. However, it does not explicitly contrast with alternatives (e.g., get_fee_forecast or get_current_fees) or state when not to use it, so guidance is only implied.

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