create_responsive_search_ad

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

Explains RSA dynamic combination behavior and dry_run validation. No annotations exist, so description covers key behavioral traits like non-execution on dry run. Lacks notes on idempotency or error conditions, but adequate.

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?

Well-structured with Args/Returns sections, front-loaded purpose. Slightly long but every sentence adds value. Could be more terse without losing clarity.

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 all parameters, return value, and dry_run behavior. Lacks mention of prerequisites (e.g., ad group existence) or error handling, but given output schema and no annotations, it is largely complete.

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%, so description provides all parameter semantics: ad_group_id, headlines with count/char limit, descriptions with count/char limit, final_url, optional customer_id, path1/path2 max chars, and dry_run meaning. Adds significant value beyond schema.

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 a responsive search ad (RSA)' and explains what RSA is. Verb+resource is specific and distinct from siblings, which lack other ad creation tools.

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 required counts and character limits for headlines and descriptions, plus Google's recommendation for variations. Implicitly guides usage but does not explicitly state when to use vs other ad types (not needed given siblings).

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