google_ads_campaigns_create

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

With no annotations, the description carries the full transparency burden. It discloses that the tool is mutating, counts against daily write quota, is not automatically reversible, and returns resource_name and id. This goes well beyond a bare 'creates campaign' statement.

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?

Every sentence earns its place: action and return, mutation warning, quota, non-reversibility, rollback pointer, prerequisite, and follow-up alternatives. The description is front-loaded with the core purpose and contains 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?

For a create tool with a rich schema and no output schema, the description fully covers return shape, preconditions, side effects, and subsequent actions. It addresses the key operational concerns (quota, reversibility, budget creation, later edits) and leaves no significant gaps.

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?

Input schema coverage is 100% with detailed descriptions and enums, so the baseline is 3. The description adds the prerequisite relationship for budget_id and mentions channel types, but otherwise duplicates the schema's parameter documentation. No significant extra parameter semantics are added.

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 opens with 'Creates a new Search or Display campaign' – a specific verb, resource, and scope. It clearly distinguishes itself from update/status siblings and from ad group creation tools, and even names the update tools for later edits.

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 budget_id prerequisite and directs users to google_ads_budget_create if missing. It also gives explicit alternatives for later edits (google_ads_campaigns_update or google_ads_campaigns_update_status) and advises recording before-state via mureo_state_action_log_append for rollback, which is clear when-to/not-to guidance.

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