google_ads_ads_create

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

With no annotations, the description carries full burden. It discloses that the operation is mutating, reversible via rollback_apply (which pauses the ad), and that initial approval status is typically UNDER_REVIEW for ~1 business day. It does not cover auth requirements or rate limits, but the key behavioral aspects are addressed.

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 sentences packed with essential information: purpose, return values, reversibility, constraints, and sibling differentiation. No fluff; every sentence serves a purpose.

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?

Given 7 parameters (all well-described in schema) and no output schema, the description covers return values, reversibility, and ad format requirements. It does not explain all edge cases or policy details, but for a creation tool with rich schema, it provides sufficient context for correct invocation.

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%, baseline 3. The description reinforces the RSA requirements (headlines 3-15, descriptions 2-4) and mentions path dependencies (requires path1 if path2 set), adding value beyond the schema. However, it mostly reiterates schema constraints without providing new contextual meaning beyond what is already in the parameter descriptions.

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 it creates a Responsive Search Ad (RSA) in a specified ad group, mentions return values (resource_name, id, approval_status), and distinguishes itself from the display ad creation sibling tool. The verb 'creates' and specific ad type make the purpose unambiguous.

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?

It explicitly tells when to use this tool (for RSAs) and directs users to google_ads_ads_create_display for display/banner ads. It also provides format requirements (3-15 headlines, 2-4 descriptions). However, it does not mention when to use other sibling tools like google_ads_ads_update or google_ads_ads_list for non-creation tasks.

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