brc_delete_payment

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

With no annotations, the description fully explains the key behavior: the two-step confirmation workflow. It does not describe other behaviors like return value types beyond mentioning 'confirmation_required and a payload preview', but this is sufficient for a delete operation.

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 is two sentences long, front-loads the purpose, and uses clear, direct language. Every part is necessary and no word is wasted.

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 delete tool with a non-trivial confirmation workflow, the description covers the essential usage pattern. It mentions the return of confirmation_required and payload preview despite no output schema. It could be slightly improved by noting that the deletion is permanent, but overall it is complete.

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 75%, and the description adds meaningful context to the confirmWrite parameter by explaining its role in the two-step process. It does not cover confirmDelete, but the main workflow is well explained.

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 deletes a BRC payment by id, and distinguishes itself from other delete tools by detailing a two-step confirmation process. It provides a specific verb and resource.

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 gives explicit step-by-step instructions on when to call without confirmWrite, to show a draft, and then retry with confirmWrite: true only after user confirmation. It also warns that preflight is not confirmation, providing clear usage boundaries.

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