ad_group_delete_preview

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

Annotations already declare readOnlyHint=true, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful context that the deletion is irreversible and the campaign must be paused, but it does not explain preview mechanics, what the output represents, or how expectedText protects against mistakes.

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 sentence with no wasted words. The core action and scope appear immediately.

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 and annotations are rich, so the description need not explain return values. However, for a destructive preview tool with a required expectedText guard, the description should clarify that this is a dry-run preview and why expectedText is required.

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 75%, with descriptions for profile, adAccountId, and expectedText, while the id parameter is undocumented. The description itself adds no parameter-level meaning, so the schema remains the primary source.

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 gives a specific verb, resource, and scope: previewing deletion of one ad group. It distinguishes itself from campaign_delete_preview and ad_delete_preview by resource, though it does not explicitly name those alternatives.

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 phrase 'under a paused campaign' implies a precondition for use, but there is no explicit guidance on when to choose this preview versus ad_group_get, ad_group_update_preview, or another delete preview. Usage is inferable but not clearly routed.

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