brc_batch_suppliers

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

Without annotations, the description fully discloses the preflight/confirmation behavior, maximum items, and the requirement for explicit user confirmation. However, it does not describe error handling, side effects, or the nature of the return value beyond mentioning confirmation_required and preview.

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?

Four sentences, front-loaded with purpose, no redundancy. Every sentence adds essential guidance (limit, confirmation workflow, non-confirmation clarification).

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 complexity of batch processing with a preflight confirmation workflow and no output schema, the description adequately conveys the core behavior. It covers the confirmation protocol and parameter semantics. Slightly lacking on what the tool returns after successful write, but schema description fills some gaps.

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 significant value by explaining the workflow around confirmWrite (two-step process) and confirmCrAnalysisCategory (intentional CR account). It also clarifies priceBasis for VAT-inclusive/exclusive. This goes beyond schema descriptions.

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 the tool processes a batch of suppliers with a specific constraint (max 5 items). Distinguishes from sibling batch tools and single supplier creation tools through naming and context.

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?

Explicitly describes the two-step confirmation process: first call without confirmWrite, show plain-English draft, then retry with confirmWrite after explicit user confirmation. Provides critical guidance on what constitutes confirmation ('passing preflight is not confirmation'). Does not explicitly state when to use alternative tools like brc_create_supplier for single suppliers.

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