brc_create_prepayment

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

With no annotations, the description discloses key behavior: the API accepts only the parent transaction shape and automatically generates a reversing child transaction. It also warns about confirmWrite usage, which is important for safe invocation.

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, each essential: first states purpose and mechanism, second provides a critical usage warning. No wasted words, information is front-loaded.

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?

No output schema exists, but the description fails to mention what the tool returns (e.g., the created prepayment or success status). It does cover the parent/child transaction behavior, but omits return value information, which is a gap for an agent.

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 context about confirmWrite (must only be true after user confirmation) which aligns with the schema, but does not significantly augment what the schema already provides for other parameters.

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?

Description clearly states it 'Creates a new parent Prepayment', identifying the specific verb-verb (create) and resource (prepayment). It distinguishes from siblings like update, delete, get by making creation explicit.

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?

Provides explicit guidance on the confirmWrite parameter: 'Do not call with confirmWrite=true until the user has reviewed the draft and explicitly confirmed creation.' This clarifies when and how to use the tool safely, though it does not explicitly contrast with alternatives.

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