google_ads_ad_groups_create

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

With no annotations, the description carries full burden. It discloses mutability, reversibility via rollback_apply (with caveat that rollback pauses rather than deletes), and failure condition for REMOVED campaigns. However, it doesn't disclose the default status of the created ad group or any other side effects.

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 four sentences, front-loading the action and return value, then behavioral notes, then prerequisites, then next steps. It is concise and well-ordered, though not perfectly compact.

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 no output schema, it specifies return values (resource_name, id). It covers prerequisites, behavior, and next steps. It is missing some error details but is generally complete for a creation tool with few required parameters.

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 100%, so baseline is 3. The description reinforces parameter constraints (e.g., name uniqueness, campaign ID validity) but adds no new information beyond the schema descriptions themselves.

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 it creates a new ad group inside an existing campaign, specifies the returned resource_name and id, and differentiates from sibling tools like list/update. It also provides context of mutability and reversibility.

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?

It explicitly states the prerequisite (campaign must be ENABLED or PAUSED) and gives recommendations for subsequent steps (add ads and keywords). It doesn't explicitly contrast with other create tools, but the purpose is clear enough for an agent to decide when to use this tool.

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