brc_delete_cash_receipt

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

With no annotations, the full burden is on the description. It thoroughly explains the two-step behavior, the necessity of user confirmation, and the preview feature. It doesn't mention error states or impacts of deletion, but the core behavior is well-transparent.

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, no unnecessary words. Front-loaded with the core action, then immediately provides step-by-step instructions. Every sentence serves a purpose.

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 a two-step deletion with confirmation, the description is remarkably complete. It covers the full workflow, the role of confirmWrite, and the need for explicit user confirmation. No output schema exists, but the preview step is implied.

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% (3 of 4 params described). The description adds significant value for 'confirmWrite' by explaining its two-step usage. Other parameters' descriptions are sufficient in the schema, and the description does not repeat them unnecessarily.

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 cash receipt by id.' It also details the two-step confirmation process, distinguishing it from other delete tools in the sibling list that may not require such confirmation.

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 explicitly instructs to first call without confirmWrite, show the preview draft in chat, and retry with confirmWrite true only after explicit user confirmation. It also warns that preflight is not confirmation, providing clear when-to-use and when-not-to-use guidance.

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