google_ads_campaigns_create

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

Discloses that the tool is mutating, counts against daily write quota, and is reversible via rollback_apply (which pauses rather than deletes). Also states it returns resource_name and id. Since no annotations exist, the description fully covers behavioral traits.

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?

Five sentences, each conveying essential information: action+returns, mutation+quota, reversibility, prerequisite, and sibling tools. No wasted words, well 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?

Given no output schema, description specifies the return (resource_name and id). Covers prerequisites, limitations (bidding strategies, channel types only Search/Display), and reversibility. Complete for a creation 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 100%, so the schema already documents parameters. The description adds context: budget_id is required and how to obtain it, bidding_strategy has defaults and limitations (TARGET_CPA/ROAS not fully exposed), and channel_type defaults to SEARCH. This adds meaning 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 creates a new Search or Display campaign in a specified Google Ads account, distinguishing it 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 the prerequisite of a pre-existing budget_id and directs to google_ads_budget_create if needed. Also mentions using google_ads_campaigns_update or google_ads_campaigns_update_status for later edits, providing clear when-to-use guidance.

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