draft_ad_group

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

Annotations indicate non-read-only and non-destructive behavior. The description adds that it returns a preview and does not create, which aligns with the annotations. It also notes the ad group is ENABLED and SEARCH_STANDARD, providing useful behavioral context beyond the structured fields.

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 brief (a few sentences) with bullet points for parameters. It front-loads the key information about the preview nature and the workflow. Every sentence adds value with no redundancy.

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 covers the tool's purpose, parameters, and the necessary next step (confirm_and_apply). With an output schema available, the lack of detail on the return value is acceptable. Overall, it provides sufficient context for an agent to use 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?

Schema description coverage is 0%, so the description compensates by explaining each parameter's purpose and format: campaign_id source, ad_group_name, keywords structure (list of objects with text and match_type), and cpc_bid_micros condition. The customer_id parameter is not explained, but it has a default value.

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 drafts an ad group and returns a preview, not a creation. It distinguishes itself from sibling tools like confirm_and_apply by specifying the draft-then-execute workflow. The ad group type and status are explicitly mentioned.

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 indicates the draft is a preliminary step before calling confirm_and_apply, providing clear context on when to use this tool and what to do next. However, it does not explicitly list alternative tools or scenarios where this should not be used.

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