Create Campaign

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

With only destructiveHint=false provided, the description adds meaningful behavioral context: the campaign starts PAUSED and cannot spend money until a human enables it. This is non-obvious, safety-relevant information not present in annotations or schema. It stops short of describing auth needs or return behavior, but output schema covers the latter.

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?

Two tightly written sentences, front-loaded with the tool's purpose and the safety-relevant PAUSED state. Every clause earns its place.

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 10-parameter creation tool with full schema coverage and an output schema, the description covers the two things an agent most needs: the creation state and the budget prerequisite. Missing only minor niceties like validation-mode guidance (though validate_only is documented in 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%, so all ten parameters are already documented in the schema (including budget_resource_name's origin and bidding strategy enums). The description only reinforces the budget dependency. Baseline 3 is appropriate.

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?

States a specific verb (Creates) and resource (campaign) and adds the crucial default state (PAUSED). This clearly distinguishes it from siblings like create_ad_group and create_campaign_budget. An agent knows exactly what this tool produces without opening the schema.

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 gives the prerequisite ('Create a budget first with `create_campaign_budget`'), which routes the agent to the correct preceding tool. It does not name exclusion conditions or alternatives, but the ordering constraint is clear context.

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