brc_delete_quote

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

Despite no annotations, the description discloses the two-step confirmation, the preview step, and the need for explicit user confirmation. It indicates the operation is irreversible but doesn't elaborate on 'timestamp confirmation.' Overall, good behavioral context.

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 wasted words. Structure is logical and easy to follow.

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 tool has 4 params and no output schema, the description covers the critical delete workflow. Missing details on 'timestamp confirmation' and return format, but sufficient for selecting the tool.

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% (confirmDelete lacks description). The description adds value by explaining the confirmWrite parameter's role in the two-step workflow, but doesn't cover confirmDelete. Baseline 3 is appropriate.

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 deletes a BRC quote by ID with timestamp confirmation. It distinguishes from siblings like brc_close_quote and brc_update_quote by specifying deletion and the confirmation workflow.

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?

Explicit guidance on the two-step process: first call without confirmWrite:true, show preview, then retry with confirmWrite:true after user confirmation. Notes that preflight is not confirmation. Lacks explicit when-not-to-use, but the context is clear.

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