create_campaign

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

With no annotations, the description carries the full disclosure burden, and it does surface one meaningful trait: campaigns are created paused for safe review. That is largely mirrored by the schema's status default of 'PAUSED', and nothing is said about permissions, budget side effects, or what happens to the returned entity.

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 front-loaded sentence with no filler; the key behavior is stated immediately. Brevity is not achieved by padding, though the sentence is arguably too terse given the parameter surface.

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?

An output schema exists so return values need not be explained, but for a 7-parameter mutation tool with zero schema descriptions and no annotations, the definition leaves too much unstated: required context, parameter meaning, and when to prefer this over the template-based sibling.

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 0% across 7 parameters, so the description was required to compensate and does not. It never explains name, objective, the daily_budget vs lifetime_budget relationship, ad_account_id, or the accepted values for special_ad_categories.

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?

States a specific verb and resource ('Create a campaign'), so the operation is unambiguous. However, it does not differentiate itself from the sibling create_campaign_from_template, leaving the agent to infer which creation path applies.

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?

No when-to-use guidance, no prerequisite conditions (e.g., required ad account context), and no mention of the alternative create_campaign_from_template. The agent gets no routing help despite several related sibling tools.

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