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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds genuinely non-redundant operational context: the tool is paywalled at 20 sats or US$0.02 USDC per call, and pay_with='lightning' returns a BOLT11 invoice plus token instead of an x402 payment request. It stops short of describing failure modes (e.g., what happens on an expired invoice or unpaid call), so it is not a full 5.

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?

Two dense sentences with the returned data front-loaded and pricing/payment mechanics second. Every clause carries information; no filler or restatement of the title. It could be marginally tighter but is well within an appropriate size for this tool.

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-required-parameter, read-only, no-output-schema endpoint, the description covers what comes back, that it is node-scoped, and the full payment flow. The main missing element is routing guidance relative to the overlapping sibling tools, which is a usage concern more than a completeness one.

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%, so both l402 and pay_with are already documented in the schema, and the enum on pay_with is structured. The description reinforces the payment/price context that motivates these parameters but adds no syntax or format detail beyond what the schema states — the baseline 3 for fully covered schemas.

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 enumerates the specific data returned (fee rates across 1 block–1 day, mempool, 24h whale transactions, AML cases, implied BTC/USD), which is far more informative than the title alone. It reads as a node-scoped market snapshot, but it never explicitly contrasts itself with siblings like bitcoin_address_risk or whale_geopolitics_report, which overlap on the whale/AML dimension.

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 statement of when to call this versus the sibling tools, and no prerequisites beyond the payment mechanics. The 'from this node' qualifier hints at scope, but an agent gets no routing guidance for choosing between this pulse endpoint and the address-risk or geopolitics reports.

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