bulkPauseCampaigns

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It confirms the pause action and mentions dry-run preview, but it does not state whether the operation is reversible, what happens on partial failure, or what the response contains. For a mutation tool, this is a significant 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?

The description is a single efficient sentence that front-loads the action and resource ('Pause multiple campaigns') and then notes the dry-run capability. Every phrase earns its place without wasted words.

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?

This is a bulk mutation tool with no annotations and no output schema, so the description should explain operational context such as return behavior, error handling, or reversibility. The current description covers the basic action and dry-run, but leaves an agent uncertain about the outcome of executing the pause.

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?

The input schema already documents both parameters: campaignIds as an array of campaign IDs and dryRun as a boolean with default false. The description adds only the idea of 'dry-run mode to preview changes,' which overlaps with the schema's dryRun property without adding new meaning.

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 states a specific verb and resource: 'Pause multiple campaigns in a single operation.' It clearly differentiates from the sibling pauseCampaign by emphasizing batch behavior, so an agent can distinguish it without inspecting the schema.

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 phrase 'multiple campaigns' implies the batch use case, and the sibling list includes pauseCampaign as a likely single-campaign alternative. However, the description does not explicitly say when to prefer this tool over pauseCampaign or mention bulkActivateCampaigns as the inverse operation.

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