cm_create_campaign

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

Description lacks behavioral details beyond 'create draft'. No disclosure of side effects (e.g., no sending, no credit consumption), required permissions, or that it returns a campaign ID. Annotations provide no readOnly/destructive hints, so burden falls on description.

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?

Single sentence, efficient, front-loaded with verb and resource. No unnecessary words.

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 10 parameters, 7 required, and no output schema, description is minimal. Does not explain return value, lifecycle (draft vs. sent), or required client context. Inadequate for an agent to understand full usage.

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 documents all 10 parameters with descriptions (100% coverage). Description adds no extra meaning beyond 'from HTML/text content', which aligns with HtmlUrl and TextUrl parameters. Baseline score applies.

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 clearly states verb 'Create' and resource 'draft campaign', and specifies input source 'from HTML/text content'. Distinguishes from sibling 'cm_create_campaign_from_template' and other creation/sending tools.

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 guidance on when to use this tool vs. alternatives (e.g., cm_create_campaign_from_template) or prerequisites (e.g., confirmed sender email). Only implies use when raw content is available.

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