manage-product-options

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

No annotations are provided, so the description bears the full disclosure burden, and it does say 'delete' removes options. However, it never states side effects: whether deleting an option cascades to variants, what variantStrategy CREATE does to existing variants (left to the schema), or any permission/rate constraints. For a mixed read/write tool with a destructive delete path, that is a meaningful gap.

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, front-loaded with purpose and then the action mapping, with zero filler. Every clause earns its place by either identifying the resource or disambiguating a mode.

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 10-parameter mutation tool with no annotations and no output schema, the description covers purpose and action modes but leaves the destructive scope of delete, the variant side effects, and any return information unstated. The detailed schema carries most of the parameter load, but the behavioral surface remains thin.

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 90%, so the baseline is 3, but the description adds real meaning beyond the schema: the 'action' enum has no per-value description in the schema, and the description explains what update actually does (rename or add/remove values) and what delete targets. The meaning of the mode switch is therefore clearer from the description than from the raw enum.

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 first sentence gives a specific verb set and resource ('Create, update, or delete product options') with concrete examples (Size, Color), so the agent immediately knows what domain this touches. It does not explicitly distinguish itself from the nearby sibling manage-product-variants, which an agent could plausibly confuse with this tool.

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?

The second sentence maps each action value to an intent ('create' to add, 'update' to rename or add/remove values, 'delete' to remove), giving clear per-mode guidance. It stops short of stating when to prefer this tool over manage-product-variants or what prerequisites (e.g. option ownership) apply.

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