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

Annotations already mark this destructive and open-world, and the description goes well beyond them: existing variants are matched by option combination and preserve id, SKU, price and stock, while missing combinations are added at the product's price, all capped at 100. That is exactly the kind of side-effect detail an agent needs before invoking a mutation.

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 core behavior is front-loaded in two dense, informative sentences with no filler. The trailing Args block is pure repetition of the parameter names with no added value, which is the only waste.

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?

An output schema exists, so return values need not be described, and the description covers the key semantics: matching rule, price default, and the 100-variant cap. It could be stronger by noting prerequisites or what happens when the cap is exceeded.

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% and the description's Args block only restates the names ('project_id: The project ID', 'product_id: The product ID'), adding no format, source, or constraint information. It fails to compensate for the schema gap.

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 ('Generate every combination of a product's current options as variants') and bounds the scope with '(max 100)'. It is clearly distinguishable from the sibling create_commerce_variant, which creates one variant, and list_commerce_variants, which reads them.

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 describes the bulk-generation behavior and the max-100 constraint, which implies the context for use, but never states when to prefer it over create_commerce_variant for a single variant or what prerequisites (e.g. options must already be defined via set_commerce_product_options) apply. Usage is implied, not prescribed.

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