ecommerce_clone_product

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

With no annotations provided, the description carries the full burden, but it only states the high-level action. It doesn't disclose whether cloning overwrites existing products, requires platform credentials, handles missing source pages, or has side effects on target stores.

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 a single front-loaded sentence with no filler; every word contributes. It is concise, though it errs slightly toward under-specification rather than providing useful operational detail.

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 multi-platform mutation tool with no annotations, no output schema, and undocumented parameters, this description is not operationally complete. An agent would not know the expected result, failure modes, or whether cloning is additive or destructive.

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%, so the description must compensate. It loosely maps sourceUrl and targetPlatforms through the phrase 'source URL to multiple target platforms', but it adds no format, allowed values, or behavior details, and translationTemplate is 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?

The description uses a specific verb ('Clone') with a clear resource ('product') and scope ('from a source URL to multiple target platforms'). It doesn't explicitly compare against sibling tools like ecommerce_sync_multiplatform_stock, but the core action is distinct enough to avoid most confusion.

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?

No guidance is provided about when to choose this tool over siblings such as ecommerce_sync_multiplatform_stock or ecommerce_product_search. There is also no mention of prerequisites like an existing authenticated session or a prior product extraction.

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