add_ad_groups

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

With no annotations, the description carries full burden. It clearly explains the dry-run capability and constraints on required fields. It does not mention permissions, rate limits, or side effects, but it is transparent about the create operation and parameter roles.

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 well-structured with a clear title and a bullet-like Args section. Each sentence provides essential information without redundancy. It is concise yet thorough.

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 complex nested object array for ad_groups, required fields, and optional fields with region ID examples. It lacks details on error handling or existence checks but is complete for a creation tool given no output schema.

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% with no descriptions in the schema. The description adds comprehensive parameter details: Name, CampaignId, RegionIds (with examples), Type, NegativeKeywords, TrackingParams, and confirm. This far exceeds the bare 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 'Create ad groups inside existing campaigns', using a specific verb and resource. It distinguishes from sibling tools like 'add_campaigns' and 'list_ad_groups', which have different purposes.

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 implies campaigns must exist and explains the confirm parameter for dry-run vs execution. However, it does not explicitly compare with alternatives like 'add_ads' or provide when-not-to-use scenarios.

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