create_campaign

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

With no annotations, the description carries full burden. It discloses default status, budget behavior, and required field nuances. It does not mention return values or error conditions, but the creation behavior is well explained.

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?

Four concise sentences, front-loaded with 'WRITE: Create a new campaign.' Every sentence adds value without redundancy. Ideal length for a creation tool.

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 complexity (9 parameters, budget strategies, required special categories), the description covers the essential workflow. It could mention return format, but without an output schema, this is acceptable. Slightly incomplete for full autonomy.

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 input schema has 89% coverage, but the description adds significant meaning: clarifies the CBO/ABO budget distinction, recommends PAUSED over ACTIVE, and explains special_ad_categories usage. This goes beyond the schema's inline descriptions.

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 explicitly states 'WRITE: Create a new campaign,' clearly identifying the verb and resource. It distinguishes from sibling tools such as update_campaign, delete_campaign, and activate_campaigns_batch.

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 guidance: recommends PAUSED as default, explains when to pass budgets for CBO vs ABO, and notes that special_ad_categories is required. It gives clear context on when and how to use this tool effectively.

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