brc_delete_supplier

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

With no annotations provided, the description carries the full burden. It discloses the key behavior: the first call returns confirmation_required and a preview, and deletion only occurs after explicit user confirmation. However, it doesn't mention the final response status or any irreversible consequences beyond the confirmation flow.

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 with no filler. The main purpose is front-loaded. Each sentence provides necessary instruction. The structure is concise and easy to parse.

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?

For a destructive tool with 4 parameters and no output schema, the description covers the critical confirmation workflow. It omits details about the final response (e.g., success indicator) and the role of confirmDelete. Still, it provides enough context for an agent to execute the two-step process correctly.

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?

The description adds significant meaning to confirmWrite with a detailed usage rule (when to set true/false). It provides a helpful example for companyName. However, confirmDelete is not mentioned at all, and id's description in schema is minimal. With 75% schema coverage, the description compensates for the key parameter but leaves confirmDelete unexplained.

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 states 'Deletes a BRC supplier by id' with a clear verb and resource. This distinguishes it from sibling delete tools like brc_delete_customer or brc_delete_accrual by also detailing the 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?

The description provides explicit step-by-step instructions: first call without confirmWrite, show plain-English draft, then retry with confirmWrite only after user confirmation. It clearly states when not to use (never set confirmWrite on first call) and that preflight is not confirmation.

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