cm_send_campaign_preview

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

The description indicates the tool sends emails, which is a write operation, but does not elaborate on effects such as sending real previews to specified recipients. Annotations provide no safety hints, so the description carries the burden but adds minimal behavioral context beyond the obvious.

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, concise sentence that front-loads the key verb and resource. No extraneous words or unnecessary 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?

For a simple preview tool with three parameters, the description provides sufficient context. It could mention that only draft campaigns are eligible or that previews are real emails, but these are not critical gaps.

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?

All three parameters are fully described in the input schema (100% coverage). The tool description adds no additional parameter information, so it does not improve over the schema.

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 action ('Send a preview/test'), the resource ('a draft campaign'), and the recipients ('to specific recipients'). It distinguishes this tool from its sibling cm_send_campaign, which sends the actual campaign.

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 usage for testing draft campaigns before sending. However, it does not explicitly state when not to use it (e.g., for live campaigns) or mention alternatives like cm_send_campaign.

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