create_variation

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

Annotations only include openWorldHint: false, so the description carries the burden of behavioral disclosure. It discloses the prerequisite that the parent must be a variable product with matching attributes, which is a key constraint. It does not mention permissions or side effects, but for a create operation this is sufficient.

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 concise sentences, front-loaded with the core action, and each sentence earns its place by providing necessary context. No redundancy.

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?

With 13 parameters, nested objects, and no output schema, the description provides key context (prerequisite, batch alternative) but does not mention return values or error conditions. However, the tool's purpose is straightforward and the schema covers parameter details, so the description is reasonably complete.

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 coverage is 100%, so baseline is 3. The description adds semantic value by saying 'matching attributes,' which clarifies that the 'attributes' parameter must align with the parent product's defined attributes. This goes beyond the schema's generic description.

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 and resource: 'Create a variation for a variable product.' It clearly distinguishes from siblings like update_variation and batch_update_variations by stating 'Use batch_update_variations for multiple at once.'

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 states when to use this tool: 'Parent product must have type="variable" with matching attributes.' It also gives an alternative: 'Use batch_update_variations for multiple at once.' This is explicit guidance on prerequisites and alternatives.

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