cm_create_campaign_from_template

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

Annotations are minimal (only title), so the description carries full burden. It does not disclose behavioral traits such as whether it requires an existing template, returns a campaign ID, or has side effects. For a write operation, more context is needed.

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 a single sentence, which is concise and front-loaded. However, given the tool's complexity (10 parameters), it is under-specified. It earns its place but lacks necessary detail.

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?

With no output schema and only a brief description, the tool is incomplete. It doesn't explain return values, prerequisites (e.g., template existence), or how it fits with sibling tools. The high schema coverage partially compensates, but the description lacks integration.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema; it does not elaborate on any of the 10 parameters or their relationships.

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 'Create a draft campaign from a saved template for a client' uses a specific verb ('Create') and clearly identifies the resource (draft campaign from a template). It distinguishes from sibling tools like cm_create_campaign (which creates without a template) and cm_send_campaign (which sends).

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 implies when to use (when a template is available) but does not explicitly state when not to use or offer alternatives. There is no guidance on prerequisites or comparison to cm_create_campaign.

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