brc_create_prepayment

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

With no annotations, the description carries full burden. It discloses that the tool creates a parent Prepayment and relies on shared logic to generate a reversing child transaction. It also warns about the confirmWrite flag, giving important behavioral context beyond simple creation.

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 sentences with no wasted words. The information is front-loaded and to the point.

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 complexity of creating a parent with an auto-generated child, the description and schema provide enough context for correct usage. No output schema exists, but description doesn't need to explain return values. The confirmWrite guidance fills a key gap.

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 baseline is 3. The description adds semantic value for confirmWrite by explaining when to set it true, but for other parameters it adds no additional meaning beyond the schema descriptions.

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 it creates a parent Prepayment, specifying the verb and resource. It distinguishes from sibling tools like brc_delete_prepayment, brc_get_prepayment, and other create tools by focusing on the prepayment entity and its parent-child aspect.

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 a critical usage guideline: 'Do not call with confirmWrite=true until the user has reviewed the draft and explicitly confirmed creation.' It does not explicitly compare to alternatives, but the resource name differentiates from other create tools.

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