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

Beyond the annotations, the description discloses the L402 payment workflow: exact-priced Lightning invoice, confirmed settlement requirement, retry with Authorization header, and the warning that invoice creation alone is not payment. It is consistent with readOnlyHint=false and idempotentHint=false, though it could be clearer about what state changes or receipt artifacts result from a paid successful call.

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 front-loaded with the core purpose and alternatives, and the payment details are important, but it contains hype and jargon such as 'eliminate temporal and factual hallucinations' and 'thermodynamic entropy.' The L402 paragraph is dense and could be tightened without losing operational meaning.

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 output schema and highly detailed input schema, the description does not need to explain return values or parameter formats. It covers the critical non-obvious behavior: payment gating, retry semantics, and alternative tools. Minor gaps remain around the exact receipt or verification outcome, but the structured schema compensates.

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%, and the schema itself explains the two exclusive modes, the optional metadata/context fields, and format constraints. The description adds no meaningful parameter-level detail beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and target: grounding an AI agent context window in Bitcoin consensus state, binding claims to difficulty, block height, and entropy. It also distinguishes itself from proof.notarize and stratigraphy.get, though the core purpose remains somewhat abstract and jargon-heavy rather than plainly stating what a successful call produces.

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?

It explicitly says when to use it (critical reasoning steps or pre-execution checks requiring deterministic verification) and names alternatives: proof.notarize for timestamping digests and stratigraphy.get for raw metrics. This gives the agent clear routing guidance.

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