google_ads_campaigns_create

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

Discloses mutability and quota impact, and reversibility via rollback_apply (with the note that reversal pauses instead of deletes). With no annotations provided, the description carries full burden; it provides key behavioral info but could add more details on permissions or error cases.

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?

A single paragraph of 5 sentences, each earning its place: purpose, return, mutability, prerequisites, alternatives. No fluff, front-loaded.

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 purpose, return values, behavior, prerequisites, alternatives, and parameter nuances. Missing minor details like name uniqueness inside account (present in schema) and potential errors, but overall comprehensive for a creation tool with no output schema.

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 description coverage is 100%, but the description adds valuable context beyond schema: for bidding_strategy it warns about missing target fields, for channel_type it explains SEARCH vs DISPLAY, and for customer_id it mentions fallback behavior. This enriches understanding.

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 action (Creates), the resource (campaign), and specifies the types (Search or Display). It also distinguishes from sibling tools like google_ads_campaigns_update and google_ads_campaigns_update_status.

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?

Explicitly states prerequisites (budget_id needed, use google_ads_budget_create if missing) and provides alternatives for later edits (google_ads_campaigns_update or google_ads_campaigns_update_status). Also mentions it is mutating and counts against quota.

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