brc_delete_sales_rep

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

Discloses the two-step preflight/confirmation behavior, including that preview is returned. Could mention permanence of deletion, but overall sufficiently transparent for a mutation tool with no annotations.

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 and workflow. Each sentence adds value, though could be slightly more concise.

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?

Description covers the deletion workflow and return preview. Lacks output schema info, but description mentions return values. Complete enough for agent to use 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?

Schema coverage is high (75%), so baseline is 3. Description adds context on confirmWrite timing but doesn't elaborate on confirmDelete. Adequate but not exceptional.

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) and resource (BRC sales rep) with a specific method (timestamp confirmation). It differentiates from sibling delete tools by referencing the 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?

Explicit instructions on when to use: first call without confirmWrite returns preview, then retry with confirmWrite: true only after user confirmation. Warns against assuming preflight as confirmation.

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