create_campaign

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

No annotations exist, so the description carries the transparency burden. It discloses enforced defaults (audience expansion, audience network, manual bidding) but lacks details on side effects, authentication, rate limits, or error handling.

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 concise with two sentences. The first sentence is redundant with the tool name, but the second adds significant value. Could be more structured with bullets.

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?

With 12 parameters (4 required), nested objects, no output schema, and no annotations, the description is insufficient. It only covers best-practice defaults but omits output format, nested object usage, and error cases.

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 50%; the tool description adds meaning for enableAudienceExpansion, offsiteDeliveryEnabled, and bidStrategy by stating enforced best practices. Other parameters like campaignGroupId, name, etc., are not explained.

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 'Create a new campaign' and distinguishes from sibling tools like bulk_create_campaigns by noting enforced best practices (audience expansion OFF, audience network OFF, manual bidding default).

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 single campaign creation with best practices, but does not explicitly state when not to use it or mention alternatives. Clear context for using it with defaults is provided.

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