brc_create_sales_rep

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

Fully explains the two-step preflight confirmation behavior, including that the first call returns a confirmation_required response and payload preview. With no annotations provided, the description carries the full burden and does so clearly.

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 a single paragraph that front-loads the purpose and then explains the process. It could be slightly more concise, but the step-by-step explanation is justified.

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 two-step confirmation complexity and no output schema, the description adequately explains the preflight process. It could mention what the payload preview contains, but overall it's complete enough for correct use.

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 100%, so baseline is 3. The description adds no additional meaning to parameters like code, name, companyName beyond what the schema already provides.

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 it creates a BRC sales rep, but does not differentiate from sibling tools like brc_batch_sales_reps for batch creation, which would help the agent choose the correct tool.

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 step-by-step guidance: first call without confirmWrite, show preview in chat, then retry with confirmWrite after user confirmation. Also warns that 'Passing preflight is not confirmation', leaving no ambiguity.

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