brc_delete_product

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

No annotations, so description carries full burden. Clearly describes destructive action (delete) and the confirmation/preview pattern. Warns that preflight does not count as confirmation, which prevents accidental deletion. Does not specify permissions or side effects, but the confirmation mechanism mitigates risk.

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?

Two sentences, front-loaded with purpose, then workflow details. No fluff. Could be slightly more structured (e.g., bullet points) but remains efficient and readable.

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?

No output schema, but description mentions return fields: 'confirmation_required' and 'payload preview'. Covers the input workflow. Missing explanation of confirmDelete parameter, but that's minor. Sufficient for a delete tool with confirmation.

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?

Adds value beyond schema by explaining the confirmWrite parameter's role in the confirmation workflow. Schema already describes id and companyName sufficiently. confirmDelete is in schema with default but not elaborated in description – minor gap. Overall, supplements schema well.

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?

Clearly states 'Deletes a BRC product by id' – specific verb and resource. Among many sibling delete tools, 'product' distinguishes it uniquely. No ambiguity.

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 two-step workflow: first call without confirmWrite returns preview and confirmation_required, then retry with confirmWrite after user confirmation. States 'Passing preflight is not confirmation' to avoid misuse. Could mention alternative delete tools for other entities, 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.