create_ad_group

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

The description adds significant behavioral detail beyond annotations: 'Always created PAUSED' and the mandate requiring a conversion pixel id. Annotations only indicate readOnlyHint=false and openWorldHint=true, so the description fills a gap with concrete startup behavior.

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?

Three compact sentences: purpose, behavioral trait, practical guidance. No fluff. The most important info (creation, paused state) comes first. Efficient and clear.

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?

With 9 parameters, nested objects, and no output schema, the description covers critical behavioral and contextual details (paused state, pixel requirement). It doesn't explain return values or default behaviors for all parameters, but the schema descriptions compensate. Overall, it is sufficiently complete for an agent to use 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 coverage is 100%, so baseline is 3. The description adds extra meaning for conversion_pixel_id (mandate, how to find, practical equivalence to account id). This goes beyond the schema's generic description, raising the score.

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 an ad group' (verb+resource) and immediately adds 'Always created PAUSED', which differentiates it from sibling tools like create_campaign or create_ad. The purpose is unambiguous and specific.

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 explains a critical prerequisite: the conversion pixel id is required and provides a practical way to find it. While it doesn't explicitly compare to alternatives or give when-not-to-use guidance, the practical context (Reddit mandate, how to obtain the pixel) is highly useful.

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