google_ads_add_campaign_exclusions

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

With no annotations, the description carries the full burden. It discloses the basic behavior (adds exclusions, returns success message) and mentions CIDR support for IP ranges. However, it does not address whether exclusions are additive or replacing, permission requirements, rate limits, or error handling.

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 Args, Returns, Note sections. It is relatively concise, though the examples add length. Every sentence adds value; no 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 the tool's complexity and lack of annotations, the description should cover more: whether exclusions are added incrementally or replace existing, duplicate handling, limits, and full return structure. Output schema exists but its content is unknown, so description must do more. It is adequate but not 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% (no descriptions in schema). The description adds significant meaning: it explains placement_exclusions as 'List of URLs/apps to exclude' with examples, and ip_exclusions similarly with CIDR note. Customer_id gets a 'without hyphens' hint, but campaign_id lacks detail. Overall, it compensates well for missing schema descriptions.

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 tool adds placement and IP exclusions to a campaign. It distinguishes from sibling tools like add_negative_keywords and set_audience_exclusions by focusing on placement and IP exclusions.

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?

The description explains what exclusions do but does not explicitly state when to use this tool over alternatives (e.g., negative keywords, audience exclusions). Usage context is implied but no direct guidance on tool selection.

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