product_duplicate

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

Annotations show non-read, non-destructive, non-idempotent. The description adds that the new product is draft, which is important behavioral context. It also mentions return payload structure for chaining.

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 two sentences, front-loaded with the action, and contains no unnecessary words. Every sentence adds value.

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?

While the purpose and workflow are clear, the lack of parameter explanations and no output schema leave gaps. The description assumes knowledge of the 'site' and 'product_id' parameters.

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?

The input schema has 0% description coverage, and the description does not explain the 'site' or 'product_id' parameters. The agent is left to infer their meaning from the tool name and context.

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 'Duplicate a product' and provides the API endpoint. It distinguishes from sibling tools like product_create and product_update by specifying the duplicate behavior and status inheritance.

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?

It explicitly advises to use product_update after editing to make the duplicate public, indicating a workflow. It could be more explicit about when not to use, but the context is clear.

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