pause_ad_account

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

With no annotations, the description must carry the burden. It discloses the primary effect (stop all serving) and reversibility via activate_ad_account, which is helpful. However, it omits other behavioral traits such as whether it's idempotent, any required permissions, impact on active campaigns or spend, and what the tool returns. This is adequate but not rich.

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 sentences, zero waste. The core purpose is front-loaded and the reversibility note is placed efficiently. Everything earns its place.

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?

The tool is simple (one optional param, no output schema), and the description covers the core action and reversal. However, because annotations are entirely absent, the description does not fully compensate: it doesn't state what happens to live campaigns, whether pausing is synchronous, or what response to expect. These gaps matter for an agent deciding whether and how to call it.

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 100%: the single parameter ad_account_id has its own description ('Optional ad account ID override'). The tool description adds no further semantic detail beyond the schema, so baseline 3 is appropriate.

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 action ('Pause the ad account') and its effect ('stop all serving'), distinguishing it from sibling pause tools for campaigns, ad groups, and ads by explicitly naming the resource. The reversal route via activate_ad_account adds clarity about its place in the lifecycle.

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 intent is obvious: use when you want to halt all ad serving for the account, not just individual entities. It does not explicitly list alternatives or exclusions, but the resource-specific wording and reversibility hint guide selection. Lacks an explicit 'use instead of pause_campaign when...' statement, so a strong 4.

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