create_ad_group

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

No annotations exist, so the description carries the disclosure burden. It reveals a critical behavior: 'Dry run unless confirm=True,' which is essential for a mutation tool. However, it does not mention other behaviors like return values or error conditions, so it is not fully transparent.

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, front-loaded with purpose, followed by key parameter semantics and a safety-critical note. Every word earns its place with no fluff.

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?

For a create operation with no output schema or annotations, the description covers the essential context: what is created, where it is placed, and the dry-run execution model. It does not elaborate on return formats or permissions, but the core usage is complete enough for an agent.

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?

The description adds meaning to cpc_bid_micros ('optional default max CPC bid in micros') and clarifies confirm's functional role via the dry-run statement. Other parameters like name, campaign_id, and customer_id are self-explanatory from their names, so the description compensates reasonably given the 0% schema coverage.

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 clear, specific verb ('Create') and resource ('a standard Search ad group under a campaign'), which distinguishes it from sibling update/create tools. It leaves no ambiguity about the tool's core function.

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 context is clear: this is the tool for creating an ad group under a campaign. It does not explicitly list alternatives or when-not-to-use, but the action and target resource are unambiguous, and sibling tools are clearly for other operations.

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