google_ads_campaigns_create

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

Discloses mutability, daily write quota impact, and irreversibility without prior state logging. Since no annotations exist, the description fully carries the burden.

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?

Four sentences, no fluff. Purpose first, then behavioral warning, prerequisite, and alternatives. Front-loaded and efficiently structured.

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 value, behavioral side effects, prerequisites, and alternatives. No gaps given the tool's complexity and sibling context.

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%, but description adds value: explains enum options context (e.g., TARGET_CPA/TARGET_ROAS limitations), default values, and prerequisite for budget_id. Exceeds baseline of 3.

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 explicitly states it creates a 'Search or Display' campaign, returns 'resource_name and id', and differentiates from sibling update tools (e.g., google_ads_campaigns_update).

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?

Clear prerequisites (pre-existing budget_id, call google_ads_budget_create if needed), explicit alternatives for edits (update/update_status), and rollback guidance (mureo_state_action_log_append).

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