brc_delete_purchase

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

No annotations are provided, so the description must fully disclose behavior. It reveals the two-step confirmation process, that the first call returns confirmation_required and a preview, and that confirmWrite must only be true after user confirmation. This adequately warns of the destructive nature and correct usage.

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 three sentences, front-loaded with the main purpose, followed by clear instructions. No extraneous text; every 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?

The description covers the essential workflow but lacks details on the 'confirmation_required' response format, the payload preview, and error cases (e.g., non-existent purchase). Given no output schema, it should provide more context for the two-step process.

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%, but the tool description adds no meaning beyond what the schema already provides. The undocumented confirmDelete parameter remains unexplained. The description does not compensate for this gap.

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 purchase by id', specifying the verb (deletes), resource (BRC purchase), and identifier (by id). It distinguishes itself from sibling delete tools by focusing on purchases, though it does not explicitly compare to others. The additional confirmation detail reinforces purpose.

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 explicit steps: first call without confirmWrite, show preview, then retry with confirmWrite only after user confirmation. It warns that preflight is not confirmation. However, it does not compare to other tools like update or other delete tools, which would improve guidance.

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