Create text campaign

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

Annotations provide basic safety info, but the description adds significant behavioral context: default manual search bids, network off, and how to override with a full bidding strategy. This goes beyond structured fields.

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?

A single sentence packed with essential information—no redundant phrases, no filler. Every word serves a purpose.

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?

No output schema exists, so return values aren't expected. The description explains key defaults and constraints, but doesn't mention optional parameters like dailyBudgetMode or endDate, though these are covered in the 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 coverage is high (83%), but the description adds value by explaining the default for biddingStrategy and unit conversion for dailyBudgetAmount. It does not cover dailyBudgetMode, but that's minor.

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 it creates a TextCampaign for Text & Image ads, names the resource and action, and distinguishes defaults for bidding strategy. This is specific and differentiates from sibling tools like update_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 implies usage for creating campaigns and describes default behavior. However, it lacks explicit guidance on when to use versus alternatives like creating other campaign types or updating.

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