Draft: create an ad group

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

With no annotations provided, the description carries the full burden. It discloses the draft behavior, that it returns a draftId, and that the actual creation happens later via confirm_write. However, it does not describe what happens to the draft if left unconfirmed or any permission requirements, leaving some gaps.

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 concise, front-loaded with the core action, and provides essential follow-up in a second sentence without waste. Parameter descriptions are also succinct and relevant.

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 tool has no annotations or output schema, so the description must convey the return value and side effects. It does state the return (draftId) and the need for confirm_write, covering the main context. It could be more explicit about the lifecycle of the draft, but overall it is sufficiently complete for a simple draft operation.

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 schema covers 67% of parameters (campaignId and startEnabled have descriptions). The main description adds value by mentioning 'inside an existing campaign', reinforcing campaignId's meaning, but does not elaborate on the name parameter. With moderate schema coverage, the description does not fully compensate for the undocumented name field.

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 the tool drafts a new ad group inside an existing campaign, with a specific verb 'draft' and resource 'ad group'. It distinguishes itself from siblings like create_campaign and confirm_write by explaining it is only a draft and requires a follow-up confirm call.

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 explicitly tells the user to call confirm_write to actually create the ad group, clarifying when to use this tool versus the confirm step. It also implies the campaign must already exist, but does not explicitly exclude scenarios or name alternative tools for creating campaigns.

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