brc_delete_payment

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

Discloses the confirmation workflow and the need for explicit user confirmation. No annotations exist, so the description carries this burden well, though it omits potential side effects or reversibility.

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?

Three sentences, front-loaded with purpose, no redundant information. Each sentence adds value.

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?

Comprehensive for a delete tool without output schema: covers the unique two-step pattern. Lacks details on success response or errors, but acceptable given the action type.

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 description adds meaning to the confirmWrite parameter beyond the schema by explaining its role in the confirmation flow. The confirmDelete parameter is not elaborated, but schema coverage is 75%.

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 'Deletes a BRC payment by id', specifying the verb and resource, and is distinct from sibling delete tools.

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?

Explicitly describes the two-step confirmation process: first call without confirmWrite for a preview, then retry with confirmWrite=true only after explicit user confirmation. Also warns that preflight is not confirmation.

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