pause_ad_group

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

With no annotations, the description must carry the behavioral burden, but it only states the action. It does not disclose side effects, reversibility, permission requirements, idempotency, or what happens to related entities such as ads.

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, front-loaded, economical sentence with no filler. It is concise, though this conciseness comes at the cost of missing useful contextual details scored elsewhere.

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 has no annotations and no output schema, and the description provides only a minimal purpose statement. It does not explain prerequisites, the role of ad_account_id, effect on the ad group's ads, or what response to expect, so an agent has too little context to invoke it confidently.

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?

Only 50% of parameters have schema descriptions, and the one description ('Ad group ID.') is largely tautological. The description adds no meaning for either parameter and completely ignores ad_account_id, leaving its purpose and optionality unclear.

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 ('active ad group'), which precisely identifies the operation and differentiates it from sibling tools like pause_ad_account, pause_campaign, and pause_ad.

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?

There is no guidance about when to use this tool versus alternatives such as archiving, deactivating, or pausing at a different hierarchy level. The word 'active' hints at a precondition, but no explicit when-to-use or when-not-to-use direction is provided.

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