ad_group_pause_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description is consistent with that. But the description adds nothing beyond structured fields: it never says what a 'preview' returns, whether it mutates state, or that an apply step is required afterward.

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?

A single short sentence with no waste, but it is under-specified rather than concise. It is front-loaded with the verb, yet the brevity leaves key semantics unexplained.

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?

An output schema exists, so return values needn't be spelled out, but for a preview tool in a large family of preview/apply siblings the description should at least signal the dry-run nature and the follow-up step. With one of three params undocumented and no workflow context, it is insufficient.

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 67%: profile and adAccountId are documented in the schema, but 'id' has no description in either place. The description does not clarify that 'id' is the ad group identifier or how it interacts with the ad account scope, so the coverage gap is left unaddressed.

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?

States a specific verb and resource ('pausing one ad group') qualified by 'preview', so the agent can tell it targets ad groups rather than campaigns, ads, or keywords. However, it does not explain what 'preview' means or distinguish this from the many sibling *_preview tools beyond the resource name.

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 on when to use this versus ad_pause_preview, campaign_pause_preview, ad_group_resume_preview, or operations_apply. The preview-then-apply workflow that presumably governs this tool family is never mentioned.

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