adgroups_create

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

No annotations are provided, so the description bears the full burden. It only states the basic creation purpose with no disclosure of side effects, permissions, idempotency, rate limits, or error behavior. This is insufficient for a mutation tool.

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?

Two sentences with no extraneous content. The first sentence immediately states the tool's purpose, providing a clear front-load.

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 is complex with 13 parameters, nested objects, and no output schema. The description only gives a high-level purpose, omitting return values, required fields (beyond schema), and error handling. This is inadequate for an AI 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 description coverage is 62%, moderate. The description adds no parameter-specific information beyond the schema; it merely reinforces that bid and targeting are involved. It does not compensate for the 38% of undocumented parameters.

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?

Description clearly states the action: 'Create an ad group within a campaign.' It distinguishes from campaign-level tools by noting that bid and targeting are set here, not on the campaign, helping differentiate from siblings like campaigns_create.

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?

Description implies that bid and targeting should be set at the ad group level rather than campaign, providing some context. However, it does not explicitly state when to use this tool versus other ad group tools (e.g., adgroups_update) or any prerequisites/alternatives.

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