batch_update_variations

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

With destructiveHint=true in annotations, the description's mention of 'delete' aligns but does not add deeper behavioral context. It describes the batch scope and variable product focus, but omits details like atomicity, partial failure handling, or what happens on errors.

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 sentences with no filler. The key information is front-loaded, covering purpose and use case efficiently.

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 moderately complex mutation tool with no output schema, the description covers purpose and use case but lacks information about return format, error handling, or whether operations are transactional. Given the schema and annotations, it is adequate but not 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 description coverage is 100%, so parameters are already well-documented. The description mentions create/update/delete actions which map to the params but adds no extra meaning or parameter-specific guidance beyond the schema.

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?

Description clearly states 'Batch create, update, or delete variations' which is a specific verb+resource combination. It distinguishes itself from individual variation tools by emphasizing 'in a single request' and efficiency.

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?

Provides guidance by stating it is 'More efficient than individual calls for setting up a variable product.' This implies when to use it (batch operations) and contrasts with individual calls, but does not explicitly state exclusions or alternative tool names.

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