create_ad_group

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

With no annotations, the description carries full burden. It discloses the critical safety behavior: default is a dry-run preview, and confirm=True executes. This is essential for a mutation tool and goes beyond the schema by emphasizing the two-step execution model. It doesn't cover permissions or reversibility, but the main risk is adequately addressed.

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 two short sentences: first states the primary purpose, second explains the dry-run behavior. Every word earns its place, with no redundancy or filler.

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?

The description is adequate for a 7-parameter tool with 100% schema coverage and an output schema. It covers the essential non-schema context: the dry-run default and confirmation requirement. It doesn't discuss prerequisites or operational effects, but these are either implied by 'create' or covered by the schema.

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%, so baseline is 3. The description's mention of confirm=True matches the schema's confirm field but adds no additional meaning to other parameters (name, status, campaign_id, etc.). It doesn't explain parameter relationships or prerequisites beyond what the schema already provides.

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 'Create a new ad group within a campaign' — a specific verb (create) with a clear resource (ad group) and scope, distinguishing it from sibling tools like update_ad_group_status or add_keywords. The purpose is immediately obvious and unambiguous.

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 description gives clear context: it creates an ad group and the dry-run/confirm execution pattern. It doesn't explicitly state when to use it vs alternatives, but no competing creation tool exists among siblings, and the context is sufficient to infer proper use.

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