brc_delete_sales_rep

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

With no annotations, the description fully discloses the confirmation mechanism, the preview step, and the requirement for explicit user confirmation. It does not contradict any 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, then concise workflow details. No wasted words.

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 delete operation with a confirmation workflow and no output schema, the description is complete. It explains the two-step process, the need for user confirmation, and the role of confirmWrite, enabling correct agent 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 coverage is 75%; the description adds critical context for confirmWrite (when to set true) but does not elaborate on confirmDelete or the companyName/id parameters beyond what schema provides. However, the workflow description compensates for most semantic gaps.

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 explicitly states the action (deletes), resource (BRC sales rep), and method (by id using timestamp confirmation), clearly distinguishing it from sibling delete tools.

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 a detailed two-step workflow: first call without confirmWrite: true returns confirmation_required and a preview; then only retry with confirmWrite: true after explicit user confirmation. It also warns 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.