Ad Groups Create Ad Group

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

Annotations already indicate a non-read-only, non-idempotent mutation. The description adds meaningful behavioral context: ad groups default to ENABLED while the campaign is PAUSED, and nothing serves until the campaign is enabled with confirm=true. This goes beyond what annotations provide, though it does not cover failure modes or auth requirements.

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 sentences with no filler: the first front-loads the purpose, and the second explains the non-obvious default behavior. Every sentence earns its place.

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 rich schema, output schema, and annotations, the description covers the key non-obvious behavior (default ENABLED status and the PAUSED campaign gating). It does not need to restate return values or parameter details because those are already present in structured fields.

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 description coverage is 100%, with all seven parameters already documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific action ('Creates'), a specific resource ('Search ad group'), and a location ('inside a campaign'). This clearly distinguishes it from sibling tools that update status, update bids, or add keywords.

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 intended use is implied by the verb 'Creates' and the campaign context, but the description does not explicitly contrast with sibling tools such as ad_groups_set_ad_group_status or ad_groups_update_ad_group_cpc_bid. The PAUSED campaign / confirm=true note provides useful workflow context, but not explicit when-to-use versus alternatives.

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