google_ads_ads_create

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

No annotations provided, so the description must cover behavioral traits. It notes mutability, reversibility via rollback, and initial approval status. It does not mention idempotency or auth, but these are less critical for a create 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?

Very concise: three sentences that front-load purpose and return value, then add constraints and sibling reference. No redundant information.

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 no output schema or annotations, the description covers mutation, reversibility, approval status, parameter constraints, and sibling differentiation. It is largely complete for a create tool, though error scenarios are not covered.

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%, but the description adds value beyond the schema: it clarifies that ad_group must be in a SEARCH campaign, recommends at least 5 headlines, and specifies display width limits for path fields. This enhances understanding.

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 explicitly states it creates a Responsive Search Ad (RSA) in a specified ad group, and distinguishes it from the sibling tool for display ads. The verb 'Creates' and resource 'RSA' are clear.

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?

Provides clear guidance on when to use this tool (for RSA) versus the display alternative, and includes requirements (3-15 headlines, 2-4 descriptions). Lacks explicit exclusion for other ad types but covers the main differentiation.

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