google_ads_set_audience_exclusions

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

No annotations provided, so description carries full burden. It describes the basic mutation (prevent showing to specific audiences) but does not disclose whether exclusions overwrite or append, or required permissions.

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 structured with action, args, returns, example, and use case. It is slightly verbose but not overly so; each sentence adds value.

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 output schema exists (as per context), description adequately covers purpose, parameters, and example. Missing error handling details, but complete for a simple exclusion tool.

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 compensates by explaining each parameter: customer_id without hyphens, campaign_id, user_list_ids as list. Example adds clarity, though could mention how to obtain user_list_ids.

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 the verb 'Exclude audiences from a campaign' with specific common use cases, making it distinct from sibling tools like adding audiences or setting signals.

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 context on when to use (exclude existing customers, converters, low-value segments) and implies exclusion vs targeting, but lacks explicit comparisons to alternatives like google_ads_add_audience_to_campaign.

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