google_ads_batch_create_ads

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

No annotations are provided, so the description carries full burden. It discloses that it creates ads and returns success/failure details, but does not mention authentication needs, rate limits, whether the batch is atomic, or any side effects. Moderate transparency but missing important operational context.

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: summary, parameter explanations, schema example, required fields, return type, and example call. Every sentence adds value, and the length is appropriate for the complexity.

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 most essentials: parameters, configuration schema, required fields, and a usage example. However, it lacks batch size limits or error handling details. Given the presence of an output schema (not detailed), it is nearly complete but could mention constraints.

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?

With schema coverage at 0%, the description adds substantial meaning: it explains customer_id format, ads_json structure with a full schema example, required fields, and constraints (headlines 3-15, descriptions 2-4). This goes far beyond the minimal schema titles.

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 multiple responsive search ads in a single batch operation,' specifying the verb (create), resource (responsive search ads), and scope (batch, multiple). It distinguishes itself from the sibling tool 'google_ads_create_responsive_search_ad' which creates a single ad.

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 usage for bulk creation via 'batch operation' and the JSON array schema, but it does not explicitly state when to use this vs the single ad creation tool, nor does it provide when-not or alternatives. The context is clear enough but lacks explicit guidance.

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