brc_delete_quote

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

With no annotations, the description fully discloses the two-step confirmation behavior, including the return of confirmation_required and payload preview, and the need for explicit user confirmation in a later message. No contradictions.

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 concise sentences that front-load the main action and efficiently explain the entire confirmation workflow without superfluous words.

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?

Covers the behavioral aspects well for a delete tool with confirmation, mentioning return values for the first call. However, without an output schema, it does not describe the final success response or error conditions, but this is acceptable given the tool's simplicity.

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 75%, so most parameters are already described. The description adds semantic value by explaining the confirmWrite usage pattern and the overall timestamp confirmation flow, though it does not elaborate on confirmDelete.

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 the tool's purpose: 'Deletes a BRC quote by id using timestamp confirmation.' It distinguishes itself from sibling delete tools by describing a unique two-step confirmation process.

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 instructions on when to use each parameter: first call without confirmWrite, then retry with confirmWrite after user confirmation. It warns against common misuse. Does not explicitly compare to alternatives like brc_close_quote.

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