google_ads_batch_enable_campaigns

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

No annotations exist, so description carries full burden. It says 'Enable' implying a state change, but fails to disclose consequences (e.g., campaigns become active, what if already enabled), permissions, idempotency, or effects on serving.

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 with clear sections (Args, Returns, Example). Every sentence adds value, and the example demonstrates usage. No filler or 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?

Has output schema (not shown) which reduces burden. Includes parameter constraints and example. However, lacks behavioral details and usage guidelines. Adequate but missing context for an agent to fully understand side effects.

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%, but description adds meaningful constraints: customer_id '10 digits, no hyphens' and campaign_ids 'comma-separated list'. This goes beyond the schema's title and type, aiding correct invocation.

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?

Description clearly states 'Enable multiple campaigns in a single batch operation,' specifying the verb (enable), resource (campaigns), and batch nature. This distinguishes it from sibling tools like google_ads_batch_pause_campaigns.

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?

No explicit when-to-use or when-not-to-use guidance. The provided example shows usage, but there is no mention of prerequisites, conditions, or alternatives. Missing context on when to prefer this over other batch status change tools.

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