brc_delete_customer

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

With no annotations, the description fully explains the safe deletion workflow (preview then confirm), adding context about confirmation_required and payload preview. It does not mention side effects or permanence, but the two-step process is well covered.

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 concise (4 sentences), front-loaded with the main purpose, and each sentence adds necessary context. No redundancy.

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 delete operation with a confirmation mechanism, the description adequately covers the workflow and parameter semantics. It lacks details on return value format or prerequisites like customer existence, but is sufficient for safe usage.

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 the baseline is 3. The description adds value for confirmWrite by explaining its role in the two-step process, but does not clarify confirmDelete. It relies on schema for id and companyName.

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 action ('Deletes a BRC customer by id'), making the purpose explicit. It distinguishes from sibling tools focusing on customers, setting it apart from other delete operations.

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 detailed usage guidelines: first call without confirmWrite to get a preview, then retry with confirmWrite: true only after explicit user confirmation. It warns against treating preflight as confirmation, ensuring safe use.

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