create_campaign

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

With no annotations provided, the description takes on the full burden of disclosure. It clearly states the dry-run behavior and the paused-by-default guarantee, which are critical safety traits. While the schema already conveys the confirm and status defaults, the description reinforces them as operational rules rather than mere defaults.

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 compact, front-loaded with the core purpose, and then provides the two most important usage caveats in just two short paragraphs. Every sentence earns its place with no redundancy or filler.

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?

Given the tool has 13 parameters and an output schema, the description does not need to explain every detail. It covers the non-obvious behaviors (dry run, paused default) that could lead to mistakes. The platform context is provided in the schema's customer_id field, so overall this is sufficiently complete.

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% for all 13 parameters, so the baseline is 3. The description mentions confirm and status, but these are already fully described in the schema; no additional parameter-level meaning is added.

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 opens with 'Create a new campaign', which is a specific verb+resource statement. It clearly distinguishes this tool from siblings like update_campaign_status or create_ad_group by targeting the campaign entity itself.

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 provides explicit usage context: dry run by default, confirm=True to execute, and the requirement to set status='ENABLED' explicitly for an active campaign. It does not name alternative tools, but the creation intent is clear and distinct from the update-oriented siblings.

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