get_v1_btc_derivatives_mempool_pressure

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

No annotations are provided, so the description carries the full burden. It discloses update frequency (every 5 min), pricing ($0.02), and category (bitcoin-onchain). It does not explicitly state read-only behavior, but this is implied by the GET method and no destructive hints. The description adds valuable temporal and cost context.

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 a single sentence that front-loads the key outputs (pressure classification, fee buckets, counts), followed by three concise facts (update interval, price, category). Every piece of information earns its place with no redundancy.

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 no output schema, the description covers the main returned components: pressure classification, fee buckets (with specific ranges), RBF count, and CPFP count. It could be improved by describing the structure or format of these fields, but it is sufficiently complete for a parameterless 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 schema coverage is 100%. According to guidelines, baseline is 4 for 0 parameters. The description does not need to add parameter semantics as there are none.

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 tool returns Bitcoin mempool pressure classification (low/medium/high/extreme), fee buckets with explicit sat/vB ranges, RBF count, and CPFP count. It distinguishes itself from siblings like get_v1_btc_derivatives_fee_curve which focuses on fee estimates, and other BTC derivative tools that cover different data.

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 mempool pressure and fee data but provides no explicit guidance on when to use this tool versus alternatives such as fee_curve or blocks_range. No when-not-to-use or prerequisites are stated.

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