ads_create_campaign

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool creates a campaign with budget and bidding strategy, but does not mention auth requirements, response behavior, whether a separate budget resource is created, or what side effects occur.

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 a single, efficient sentence with no filler. It front-loads the primary verb and resource and earns its place without 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?

This is a complex mutation tool with a nested campaign object, no output schema, and no annotations. The description is too minimal to fully guide the agent: it omits usage boundaries, behavior after creation, and guidance on conditionally relevant parameters like bidding strategy and targets.

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?

The description adds high-level context that budget and bidding strategy are part of creation, which maps to schema fields like budgetAmountMicros and biddingStrategyType. However, schema description coverage is only 50%, and the description does not clarify optional fields such as targetRoas, targetCpaMicros, startDate, or endDate.

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 uses a specific verb and resource: 'Creates a new Google Ads campaign.' It clearly differentiates itself from sibling tools like ads_update_campaign and ads_list_campaigns by emphasizing creation of a new campaign.

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 makes the creation use case clear, implying it is the right tool when a new campaign is needed. It does not explicitly name alternatives or state when not to use it, but the contrast with update/list siblings is reasonably evident.

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