copy_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. It does disclose two non-obvious traits: source row IDs are not reused, and apply is gated on a fresh preview's exact scope plus confirmation hash. It does not say what replace mode does to the target's existing config, whether the change is reversible, or what permissions are needed.

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 dense sentences with no filler, and the preview-vs-apply constraint is front-loaded in the second sentence. Slightly compressed relative to the amount of behavior an agent still needs.

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?

This is a high-complexity mutation with a nested confirmation object, 18 parameters, no annotations, and no output schema. The description covers the preview/apply gate but omits the semantic difference between modes, the meaning of the confirmation fields, and the consequences of applying, leaving significant gaps for an agent.

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 18 parameters, so the description must compensate. It hints at sections and the confirmation scope/hash, but leaves mode (patch vs replace), dryRun, previewToken, idempotencyKey, allowInactiveComponents, and the eight expected* hash parameters entirely unexplained.

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/copy) and resource (manufacturing sections from one product to another), and the 'without reusing source row IDs' clause signals a distinct behavior. It is distinguishable from set_product_manufacturing_config and audit_product_group_manufacturing, but it never names a sibling to sharpen the boundary.

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?

The description implies the two-phase workflow (preview first, then apply with the returned scope and hash), which is useful invocation guidance. However, it gives no explicit when-to-use/when-not direction versus the nearby set_product_manufacturing_config, compare_product_boms, or audit_product_group_manufacturing.

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