Anchor to Bitcoin

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 that it aggregates unanchored roots and submits to OTS calendars, which gives some behavioral context, but it does not mention side effects, reversibility, or result outcomes. No contradictions with annotations (none present).

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 concise sentences that front-load the main purpose and process. No filler words.

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 tool with one optional parameter and no output schema, the description explains the core action but omits the 'status' action (available in schema) and does not describe what is returned after submission. The absence of annotations and output schema means more was expected.

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 coverage is 100% and the only parameter 'action' is fully described in the schema with enum values and a default. The description adds no additional parameter detail beyond the schema, so baseline 3 applies.

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 uses specific verbs ('Request', 'Aggregates', 'submits') and clearly identifies the resource (Bitcoin anchor of pending ledger Merkle roots via OpenTimestamps). It distinguishes from sibling tools like audit, seal, verify by describing a distinct anchoring process.

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 (when you want to anchor roots) but does not explicitly state when to use it over alternatives, nor does it mention exclusions. It doesn't reference the 'status' action available in the schema, providing only partial guidance.

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