set_product_manufacturing_config

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

With no annotations, the description carries the full burden and does disclose a non-obvious behavioral trait: the operation is concurrency-checked and apply requires a hash-bound confirmation produced by a fresh preview. It still omits permissions, idempotency behavior (idempotencyKey is in the schema but unexplained), and how removals or partial failures are handled.

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 tight sentences, no filler, with the preview/apply distinction and the confirmation-hash precondition front-loaded. Every clause carries weight.

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 19-parameter, deeply nested mutation tool with no annotations and no output schema, the description covers the single most safety-critical fact (preview -> hash -> apply) but leaves most of the argument surface unexplained. Adequate as a guardrail, incomplete as a usage contract.

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 description coverage is 0% across 19 parameters, so the description must compensate and largely does not. It vaguely gestures at BOM, operation templates, and settings (components, productOperations, autoAssemble) but says nothing about mode 'patch' vs 'replace', dryRun, idempotencyKey, the expected* hash guards, or the remove* arrays.

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?

States a specific verb pair (preview/apply) and a precise resource: product BOM, operation-template, and manufacturing-settings configuration. It is clearly the mutating 'set' counterpart to read-oriented siblings like get_bill_of_materials or copy_product_manufacturing_config, though it never names a sibling explicitly to draw that line.

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?

Gives a clear workflow rule: preview first, and apply only with the exact full confirmation scope and hash from a fresh preview. That is genuinely actionable guidance. It stops short of stating when to prefer this tool over upsert_product or copy_product_manufacturing_config, or what happens when the concurrency check fails.

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