google_ads_batch_pause_campaigns

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

No annotations provided; the description only states it pauses campaigns (a destructive action) but omits prerequisites (e.g., permissions), error handling for invalid IDs, behavior on partial failures, or any rate limits. The return is vaguely described as 'Batch operation result.'

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 short and front-loaded with the action; includes an example. Slight redundancy with schema but acceptable; no wasted sentences.

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?

Despite existence of an output schema, the description lacks completeness for a batch operation: no mention of batch limits, error handling, or what 'Batch operation result' contains. For a mutation tool with no annotations, more behavioral context is needed.

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 0%, so the description must compensate. The 'Args' section adds meaning beyond the schema: customer_id format (10 digits, no hyphens) and campaign_ids as comma-separated list. However, it does not specify that IDs are numeric or maximum length, and the description is minimal.

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 explicitly states 'Pause multiple campaigns in a single batch operation,' clearly indicating the verb (pause) and resource (campaigns), and distinguishes from sibling tools like batch_enable_campaigns.

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?

No explicit guidance on when to use this tool vs. alternatives (e.g., pausing campaigns individually or using batch_status_change). The example implies usage but lacks context about when it's appropriate.

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