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 that the operation is mutating and not automatically reversible, suggests logging for rollback, and states the expected return values. This provides solid behavioral context, though it could mention authorization needs or rate limits.

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, each serving a purpose: what it does, return values, mutability warning, prerequisites, and next steps. It is front-loaded and free of fluff, earning a high score.

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 tool's moderate complexity, no output schema, and high schema coverage, the description covers the core purpose, prerequisites, side effects, and follow-up actions. It lacks details on error conditions beyond campaign status, but overall is sufficient for an agent to understand and invoke the tool correctly.

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?

All four parameters have full schema descriptions (100% coverage), so baseline is 3. The description adds some context for campaign_id (state requirement) but largely repeats what's already in the schema (e.g., customer_id fallback, cpc_bid_micros inheritance). No significant new parameter insight beyond schema.

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 'Creates a new ad group inside an existing campaign' with a specific verb and resource. It distinguishes from sibling tools like list and update by indicating it is a create operation returning the new resource's name and id.

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?

Explicitly provides when to use (creating ad groups), prerequisites (campaign must be ENABLED or PAUSED), and actions before (log state) and after (add ads, keywords). It also warns about irreversibility, giving clear usage guidance.

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