ads_create_video_ad_group

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

No annotations are provided, so the description carries the behavioral burden. It discloses a dry-run/apply gate ('confirm: must be true to apply'), a prerequisite about the parent campaign bidding type, and the meaning of the default ad_group_type. It does not discuss side effects such as irreversibility or permission requirements, but the critical creation behavior is clear.

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 front-loaded with purpose and routing, then a compact Args list. The enumerated ad_group_type values and confirm explanation are necessary because the schema lacks descriptions and enums, and there is no wasted prose.

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 7-parameter creation tool with no annotations, it covers purpose, alternative, preconditions, parameter semantics, enum choices, and confirmation behavior. An output schema exists, so return-value documentation is not required; it only leaves implicit which fields are mandatory.

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 0%, and the Args section fully compensates: it explains customer_id format, campaign relationship, cpv_bid units, valid ad_group_type values, status values, and the confirm dry-run behavior. This goes well beyond the schema's bare property names and defaults.

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?

States a specific action ('Create a video ad group') and bounds it to a VIDEO campaign. The explicit 'Use this (not create_ad_group) for video campaigns' names the sibling it is distinct from, so an agent can disambiguate immediately.

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?

Provides an explicit routing rule: use this tool, not ads_create_ad_group, for video campaigns. It also gives conditional guidance (default ad_group_type for skippable in-stream TrueView, cpv_bid semantics) and a hard prerequisite (parent campaign VIDEO + MANUAL_CPV), so there is no ambiguity about when and how to invoke it.

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