pause_campaign

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

With no annotations, the description must reveal behavioral traits. It discloses the preview mode and allowlist requirement, but lacks details on idempotency, reversibility, or success/failure states. The output schema exists but is not referenced.

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 sentence with no unnecessary words; it is maximally concise while conveying the core action and key conditions.

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 output schema exists, the description need not cover return values. However, it omits important context such as the tool's effect on campaign state, prerequisites beyond allowlist, and how it relates to sibling pause/enable tools. It is minimally complete for a basic task.

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 adds meaning to the 'confirm' parameter (preview vs actual pause). The other parameters ('campaign_id', 'customer_id') are self-explanatory from names, and schema coverage is 0%, but the description compensates for the key non-obvious parameter.

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 the verb 'Pause' and resource 'campaign', distinguishing it from sibling tools like 'pause_ad' or 'pause_ad_group'.

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 mentions the allowlist requirement and preview behavior, providing some usage context, but does not explicitly contrast with alternatives or specify when to use this tool over others.

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