Update VWO campaign status

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

Annotations indicate destructiveHint=true, and the description adds context by stating it 'directly changes what live visitors see and can end data collection,' which aligns with and expands on the destructive nature. No contradictions with annotations.

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 short, front-loaded sentences. Every sentence adds value: the first states the core action and impact, the second provides usage context on bulk endpoint behavior.

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?

Given the destructive nature, the description adequately covers the effect on live visitors and data collection. No output schema exists, but for a mutation tool this is acceptable. The description is complete enough for an agent to decide usage.

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% and the description does not add significant details beyond the schema. It mentions 'VWO takes the campaign ids in the body,' which is a minor addition, but the schema already describes the body as opaque. Baseline 3 is appropriate.

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 starts with 'Start, pause, or stop campaigns,' which is a specific verb-resource combination clearly indicating the tool's action on campaigns. This distinguishes it from sibling tools like vwo_update_campaign or vwo_new_campaign.

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 description explicitly advises confirming campaign and target status with the user before use, providing a clear when-to context. It also notes the bulk endpoint behavior, though it does not explicitly list alternatives for when not to use.

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