pause_ad

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

Discloses the key behavioral trait of previewing unless confirm=true. With no annotations, this description does well to inform the agent of the tool's non-destructive preview mode. It does not cover other aspects like reversibility or auth, but the preview behavior is critical.

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?

Extremely concise with no redundant words. The single sentence front-loads the essential action and behavior. Could include a bit more context without losing conciseness, but it is well-structured.

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 presence of an output schema, return values are covered. However, the description lacks prerequisites or when to use this tool vs enable_ad or pause_ad_group. The preview behavior is explained, but overall context for a mutation tool is somewhat sparse.

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 only adds meaning to the 'confirm' parameter. The other three required parameters (customer_id, ad_group_id, ad_id) are left unexplained, though their names are self-explanatory. Schema coverage is 0%, so the description partially compensates.

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?

Clearly states the verb 'Pause' and resource 'ad (ad group ad)', which distinguishes it from sibling tools like pause_ad_group or pause_campaign. The specificity makes the tool's purpose unambiguous.

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?

Provides explicit guidance on the preview behavior and the confirm parameter, telling the agent that previews occur by default and actual pausing requires confirm=true. However, no explicit when-to-use vs alternatives is stated.

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