google_ads_batch_create_ad_groups

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

With no annotations, the description adds context by explaining the JSON configuration structure and required/optional fields. However, it lacks details on idempotency, ordering, error handling, or batch limits that would help the agent anticipate 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?

Structured with clear sections (intro, args, schema, returns, example). Front-loaded with purpose. The code block is helpful but adds length; still efficient overall.

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?

Covers key aspects: how to call, parameter meanings, configuration structure, and example. Missing details like maximum batch size or error behavior, but adequate for a batch tool with output schema present.

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%, but description compensates well: explains customer_id format, ad_groups_json as JSON array, and provides a detailed schema with required/optional fields and example. Could be more precise on data types (e.g., cpc_bid as number).

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?

Clearly states 'Create multiple ad groups in a single batch operation,' specifying the verb, resource, and batch nature. Distinguishes from sibling 'google_ads_create_ad_group' by emphasizing batch.

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?

Implies usage for creating multiple ad groups at once, but does not explicitly state when to use this vs. alternatives (e.g., 'google_ads_create_ad_group'). No when-not or exclusion guidance provided.

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