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

No annotations are provided, so the description carries full behavioral transparency burden. It discloses the operator-only restriction, background nature, long confirmation time, and zero cost. These are key behavioral traits. It does not describe failure modes or status checking, but the sibling 'weather_get_notarization_proof' likely covers that.

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 consists of three concise, front-loaded sentences. The first sentence captures the core action, the second adds access and timing context, and the third clarifies cost. Every sentence adds value 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 parameters and presence of an output schema (context indicates it exists), the description adequately covers what the tool does and its behavioral characteristics. It could mention the output or how results are returned, but the output schema likely fills that gap. The description is complete for an operator-only background task.

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%. The description adds no parameter information, which is appropriate since none exist. The baseline for 0 parameters is 4, and the description meets that standard.

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 states 'Build a Merkle tree of all patron balances and submit the root to Bitcoin via OpenTimestamps,' which is a specific verb+resource. It distinguishes from sibling tools, as none of the listed siblings perform this ledger notarization function.

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 provides clear context: 'Operator-only background task. Bitcoin confirmation takes 1-6 hours. Free — no credits required.' This informs when and by whom the tool should be used, and sets expectations about duration and cost. It does not explicitly exclude alternative tools, but given the uniqueness of the task, further guidance is unnecessary.

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