brc_update_supplier

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

Discloses the two-phase commit behavior and the need for a plain-English draft before finalizing. While annotations are missing, the description covers key behavioral traits. Lacks details on destuctiveness or permissions, but sufficient for a mutation tool.

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?

Single paragraph that efficiently packs essential information. Could be slightly more concise, but no superfluous text. Front-loaded with the main action.

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-phase workflow and 5 parameters, the description fully explains the process, including what the first call returns (confirmation_required and payload preview). Without an output schema, this is adequate for the agent to invoke 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 covers all parameters, but description adds crucial context: explains the conditional confirmWrite workflow and clarifies that 'payload' is an alias for 'updates'. Baseline 3 is elevated because description adds meaning beyond 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?

Description clearly states 'Updates a BRC supplier using merged fields.' It identifies the specific resource (supplier) and action (update), distinguishing it from other update tools like brc_update_customer or brc_update_product.

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 draft, then retry with confirmWrite true only after explicit user confirmation. Warns that 'Passing preflight is not confirmation,' which prevents misuse.

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