pause_campaign

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

Since no annotations are provided, the description carries the full burden. It discloses that pausing stops ad serving but preserves settings and history, and explains the dry_run parameter's validation-only behavior. However, it does not mention reversibility or error states.

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 concise: a single sentence explaining the action, followed by a structured Args list. No unnecessary words, and the key 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 the simplicity of the tool (3 parameters, no nested objects), the description covers the main effect, parameter meanings, and return value. It could mention idempotency or behavior when already paused, but overall it is sufficiently complete.

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 has 0% description coverage, so the description must compensate. The Args section adds clear semantics for all three parameters: campaign_id (what to pause), customer_id (optional, from config), and dry_run (validate vs execute). This fully compensates for the missing schema descriptions.

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 clearly states 'Pause a campaign' and explains that it stops ad serving while preserving settings and history. It distinguishes from sibling tools like 'pause_ad_group' and 'enable_campaign' by specifying the resource (campaign) and action (pause).

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 implies usage: use this tool to pause a campaign. However, it does not explicitly state when to use it versus alternatives like 'enable_campaign' or 'pause_ad_group', nor does it provide exclusions or prerequisites.

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