Pause ad

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

Annotations already declare destructiveHint=false and readOnlyHint=false; the description adds the agent-facing instruction that no confirmation is required, which is not derivable from the annotation set. It does not disclose whether the pause is reversible, what happens if the ad is already paused, or how quickly it affects delivery, which for a mutation tool are meaningful omissions.

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 compact sentences with the action front-loaded and no wasted wording. The compression is slightly excessive, since "Safe" is ambiguous on its own and the second clause is the only concrete piece of guidance in the whole definition.

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 one-parameter mutation with a fully documented schema and no output schema, the description covers the action and the confirmation policy, which is most of what an agent needs. The remaining gap is post-action behavior, such as reversibility and idempotency, which is a real but modest omission at this complexity level.

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?

There is a single required parameter with 100% schema description coverage and a pattern constraint, so the schema fully carries the semantics. The description adds nothing about ad_id, which is acceptable at this coverage level but yields only the baseline.

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 uses a specific verb plus resource ("Pause an ad"), which lets an agent distinguish it from pause_campaign and pause_ad_group by object scope. It stops short of explicitly contrasting itself with the archive_* siblings, which are the nearest ambiguity for an agent deciding how to stop delivery.

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 confirmation needed" implies this is safe to call without user approval, which is a usable usage cue. There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as archive_ad for permanent removal versus pause for temporary stopping.

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