google_ads_ads_create

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

Discloses the mutation is not automatically reversible and recommends logging for rollback. Also reveals initial approval status and typical review timeline (~1 business day). While comprehensive, it omits details like required permissions or rate limits, but overall adds meaningful behavioral context beyond the input schema.

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?

Description is concise (4 sentences), front-loaded with primary action and return values, then mutation warning, then constraints and sibling reference. Every sentence provides value without redundancy.

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 100% schema coverage and no output schema, the description covers all essential aspects: purpose, return values, mutation nature, input constraints, campaign type restriction, and relation to sibling tool. It also cross-references the logging tool for rollback, making it self-contained and actionable.

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 100%, so parameters are fully described. The description adds no new parameter-level details beyond reinforcing constraints already present in the schema (e.g., headlines count, campaign type). Baseline score of 3 is appropriate.

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 it creates a Responsive Search Ad (RSA) in a specific ad group, lists return values (resource_name, id, approval_status), and distinguishes from the display ad create tool, leaving no ambiguity about the tool's function.

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?

Explicitly names the sibling google_ads_ads_create_display for display ads, states the RSA is not interchangeable, and provides specific input constraints (3-15 headlines, 2-4 descriptions) along with a suggestion to log state for rollback, offering clear when-to-use and when-not-to-use guidance.

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