gold_create_product

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly warns 'Destructive' and states 'requires PRO' and 'BYOK fail-closed', covering side effects and a key failure mode. It does not describe response or error behavior, but the most important behavioral traits are present.

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 one compact sentence and contains almost no filler. The endpoint, destructive warning, BYOK behavior, and PRO requirement are all decision-relevant. The 'Gold PRO $29' prefix is slightly extraneous but does not unduly bloat the description.

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?

The description gives essential high-level context for a mutation tool, but with 14 parameters, no output schema, and no annotations, it leaves invocation details like the confirm gate and result shape unexplored. The schema fills some gaps, but the definition is not fully complete on its own.

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 only about 7%, and the description itself adds no meaning for any of the 14 parameters. It does not mention that name is required or that confirm must be set to CONFIRM, leaving the low-coverage schema to carry the entire parameter burden.

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 clearly states the verb and resource: 'create Woo product via POST /wp-json/wc/v3/products'. This is specific enough to distinguish it from sibling tools like gold_update_product and gold_list_products without needing to inspect their schemas.

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 usage scenario is implied by the verb 'create' and the tool name, but the description does not explicitly say when to prefer this tool over alternatives like gold_update_product. It does provide prerequisite context with 'requires PRO' and 'BYOK fail-closed'.

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