replicate_campaign

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

No annotations provided, so description carries full burden. Discloses new campaign is created in draft status, mentions authentication and rate limits, and notes it respects read-only and dry-run modes. Does not explicitly cover error handling but covers key behaviors.

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?

Description is extremely concise with 5 sentences covering all critical aspects: purpose, usage, authentication, parameter, return values, and example. No fluff, well-organized.

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's simplicity (1 required parameter, clear action), the description fully covers purpose, usage, parameter, return schema, and example. It also mentions rate limits and dry-run behavior, making it complete and actionable.

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?

Single parameter campaign_id has no schema description, but the description provides a clear explanation, an example value, and how to obtain it (from list_campaigns), adding good semantic value.

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?

Description uses specific verb 'clone' and resource 'campaign', and explicitly distinguishes from create_campaign by stating 'Use create_campaign instead to build from scratch.'

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?

Clearly states when to use ('reuse a successful campaign as a starting point') and when to use alternatives (update_campaign, set_campaign_content, create_campaign). Notes it works on campaigns of any status.

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