pause_campaigns_batch

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

Discloses key behaviors: WRITE operation, batch API usage, chunking, rate-limit handling, and specific return format. With no annotations, this is strong, though could mention partial failure behavior.

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 dense sentences, front-loaded with primary action and limits. Every word adds value, no filler.

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?

With only one parameter and no output schema, the description covers purpose, behavior, limits, and response structure thoroughly, leaving no obvious gaps.

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?

Parameter 'campaign_ids' is fully described in schema (100% coverage) as 'Meta Campaign IDs to pause'. Description adds no extra meaning beyond what the schema provides, so baseline 3 applies.

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?

Description clearly states the action (pause), resource (campaigns), and scope (bulk batch). The WRITE label and specific verb 'pause' distinguish it from siblings like 'activate_campaigns_batch' and individual update tools.

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?

Provides explicit limits (50/request), automatic chunking, and 2s delay to avoid rate limits. While it doesn't directly compare to alternatives, the batch context and sibling names imply when to use this vs. individual updates.

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