Pause or resume

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

Beyond the readOnlyHint=false annotation, it discloses the cascade effect of pausing a campaign, the lack of an ad-level pause switch, and the exact confirmation policy. These are meaningful behavioral details that prevent misuse.

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?

Four short, purposeful sentences with no filler. The core action is front-loaded, and the following sentences add essential edge cases and confirmation behavior in compact form.

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?

For a mutating tool with no output schema and sparse annotations, it covers state values, cascading effects, the ad-level limitation, and the confirm rule. The main gap is not explicitly mapping LINE_ITEM to the phrase 'ad group', though the enum makes this inferable.

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?

With only 20% schema description coverage, the description compensates by mapping entity to campaign/ad group and status to ACTIVE/PAUSED, and by defining confirm semantics. entity_id is still only explained by its name, and account_id is covered by the schema.

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 opening sentence names a specific verb and resource: setting a campaign or ad group to ACTIVE or PAUSED. It also distinguishes this from deletion by stating ads have no on/off switch, so an agent knows this tool only targets campaigns/ad groups.

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 gives clear exclusions and alternatives: do not try to pause an ad; instead pause the group or delete the ad. It also provides firm guidance on when confirm=true should be set. It does not explicitly name a sibling tool, but the boundary conditions are clear.

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