activate_campaigns_batch

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

With no annotations provided, the description fully discloses behavior: it is a WRITE (BULK) operation, runs a pre-flight ads_volume check, returns warnings, and starts spend immediately. This is adequate transparency for safe usage.

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 three sentences, each serving a purpose: purpose, behavioral detail, and usage guideline. No unnecessary words, and the most important information is front-loaded.

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 no output schema and no annotations, the description covers the key aspects: what it does, the pre-flight check, warnings, and user confirmation. It could mention response format or error handling, but it is sufficient for a batch tool.

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 description explains the skip_preflight parameter and the pre-flight process, adding context beyond the schema. The campaign_ids parameter is implied to be the list of campaigns to activate. Schema description coverage is 50%, but the description compensates well.

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 'Activate many campaigns in one Batch API call,' which is a specific verb+resource+mode. It clearly distinguishes from siblings like 'pause_campaigns_batch' and individual 'update_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?

It explicitly states 'Agents MUST confirm with the user before calling this (activation starts spend immediately).' This provides clear when-to-use guidance. However, it does not mention when not to use or suggest alternative tools like individual activation.

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