brc_create_sales_rep

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

Discloses the two-phase workflow (preflight returns confirmation_required and preview, actual write on second call) and warns that preflight is not confirmation. No annotations existed, so the description carries the burden well.

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 two sentences, front-loaded with purpose. The workflow detail is necessary but could be slightly more concise (e.g., bullet points). 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?

Given no output schema, the description mentions 'payload preview' but does not specify its structure or indicate that the output likely contains the created rep's ID. Lacks mention of prerequisites like company context existence.

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?

All parameters have schema descriptions (100% coverage), so baseline is 3. The description adds context for confirmWrite's preflight behavior but does not enhance understanding of other parameters beyond the schema.

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 'Creates a BRC sales rep', using a specific verb and resource. It distinguishes from sibling tools like batch creation and update tools by implying a single-entity creation with a confirmation workflow.

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 clear step-by-step guidance on using confirmWrite: first call without, show preview, then retry with confirmation. However, it does not mention when to use batch creation (brc_batch_sales_reps) as an alternative.

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