Create Ad Group

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the currency note. For a mutation tool it does not state whether the call is reversible, what the confirm_token does or whether it is required, what errors occur for an invalid campaign_id, or whether creating an ad group starts serving/spending immediately.

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 front-loaded sentence with the key constraint in parentheses. Every clause carries information and there is no filler or redundancy.

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 need not be described. However, for a five-parameter write tool with no annotations and zero schema documentation, the description omits the confirm/confirmation workflow and all parameter meanings, leaving the agent without enough to call 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?

Schema description coverage is 0%, so the description must compensate, and it only clarifies default_cpc (account currency). The four other parameters — customer_id, campaign_id, name, and especially the optional confirm_token — receive no explanation of format, source, or expected use.

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 names a specific verb and resource ("Create an ad group") and adds a real constraint the name does not convey: the parent campaign must already exist. It also clarifies that the CPC value is denominated in the account currency. It stops short of distinguishing itself from siblings like create_search_campaign, which also create campaign-level objects.

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 only usage context is the phrase "in an existing campaign," which implies a prerequisite but names no tool for locating a campaign_id. No guidance on when to use this versus create_search_campaign, and no mention of when a confirm_token is expected.

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