duplicate_campaign

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

With no annotations, the description fully covers behavioral traits: all created objects are PAUSED, creative references are reused, and the same-account constraint. This is comprehensive and goes well beyond the schema.

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 well-structured with a brief overview, critical behavioral notes, and an Args section. Every sentence provides essential information without redundancy.

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 6 parameters and no output schema, the description adequately explains input behaviors and constraints. However, it lacks information about the return value and error handling, which would be helpful for completeness.

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?

Though schema coverage is 0%, the description explains 5 of 6 parameters (campaign_id, account_id, name_suffix, include_adsets, adset_budget_override) with defaults and constraints. The include_ads parameter is mentioned in the behavioral text but not explicitly described in the Args section, a minor gap.

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 the verb 'Duplicate' and the resource 'campaign' with optional child objects. It distinguishes from sibling tools like duplicate_adset by specifying 'within the same account' and the scope (campaign level).

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 explicitly states when to use (duplicate campaign) and warns against cross-account duplication. However, it does not provide explicit alternatives for when to use a different tool (e.g., duplicate_adset for individual ad sets).

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