Resume paused enrollments in a campaign or smart list to continue outreach to selected contacts.
Resume paused enrollments for a campaign or smart list.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | No | Resume enrollments in this campaign | |
| smartListId | No | Resume enrollments for contacts in this smart list |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It indicates a state-changing operation ('resume paused enrollments') but does not disclose permissions, effects on already active enrollments, reversibility, or batch behavior.
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 front-loaded sentence with zero wasted words. It immediately states the verb, resource, and scope.
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 low-complexity batch mutation tool with two well-documented parameters, the description covers the core action and targeting. However, with no annotations and no output schema, it should ideally clarify mutation side effects, permission needs, or the expected result.
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 both parameters are already documented in the input schema. The description reinforces the campaign-or-smart-list targeting but does not clarify whether exactly one of the two optional parameters is required or add constraints beyond 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 uses a specific verb, 'Resume,' with a clear resource, 'paused enrollments,' and scopes it to a campaign or smart list. It is easily distinguishable from sibling tools such as conduyt_batch_pause_enrollments and conduyt_batch_stop_enrollments.
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 that this tool is used when paused enrollments should be resumed, and it distinguishes campaign vs. smart list targeting. However, it does not explicitly state when to use this instead of pause/stop tools or what prerequisites must be met.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.