create_campaign

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

With no annotations, the description carries the full burden and discloses critical behavior: the campaign defaults to PAUSED and never spends until explicitly enabled, and it returns the new campaign_id. This is valuable context beyond a simple create operation, though it does not cover permissions or error scenarios.

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?

The description is two sentences long, front-loaded with the core action, and contains no filler or redundant information. Every clause adds value: the campaign type, the default status, and the return value.

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?

The tool is simple with 4 parameters and an available output schema. The description covers the essential behavioral context (default PAUSED, returns campaign_id) and the schema documents the parameter requirements. It could mention required fields or account_id context, but overall it is sufficiently complete for this low-complexity 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 description coverage is 0%: the description does not mention any of the four parameters (account_id, name, daily_budget, status). It provides no additional meaning beyond the schema, which already has types and a default for status. The description fails to compensate for the low coverage.

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 ('Create'), the resource ('Search campaign'), and a key differentiator ('Manual CPC'). It distinguishes this from siblings like create_ad_group and build_search_campaign by specifying the exact campaign type and bidding strategy.

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?

The description implies usage for creating a new Search campaign but does not explicitly mention alternatives or when not to use this tool. It gives context about the default PAUSED state, which helps the agent understand the workflow, but it lacks explicit exclusions or references to sibling tools like build_search_campaign.

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