google_ads_add_audience_to_campaign

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

No annotations are provided, so the description must carry the burden. It explains the two modes and returns a success message, but does not disclose whether audience targeting is additive or replaces existing settings, nor does it mention permissions or error conditions.

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 with a clear purpose, separate sections for modes, args, examples, and a recommendation. Every sentence is informative and there is 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?

With an output schema available, the description need not detail return values. It covers essential aspects: operation, parameters, modes, and best practice recommendation. Missing prerequisites (e.g., user list must exist) and potential side effects, but is sufficiently complete for an additive operation.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: customer_id format, campaign_id, user_list_id, and targeting_mode with two options and a default. Examples illustrate usage clearly, adding significant value beyond the 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?

The description clearly states it adds audience targeting to a campaign and explains two distinct modes (OBSERVATION and TARGETING). It distinguishes from sibling tools like google_ads_add_audience_to_ad_group by specifying the campaign scope.

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 explicit recommendations on when to use each mode (start with OBSERVATION) and explains the purpose of each mode. However, it does not compare with other audience-related tools (e.g., google_ads_set_audience_exclusions) or state when not to use this tool.

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