Pause, resume or cancel a campaign

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

The description explicitly states 'Cancel cannot be undone,' which directly contradicts the annotation destructiveHint: false. This is a serious inconsistency that could mislead an agent about the reversibility of the cancel action.

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?

Two tight sentences front-load the core actions and then add essential behavioral details; every sentence earns its place with no fluff.

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 an output schema and annotations present, the description covers the key behaviors (pause unsent messages, cancel irreversibility) but is thinner on resume behavior and fails to reconcile with the contradictory destructiveHint annotation.

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 coverage is 50% (id is documented, action enum is not). The description adds meaning to the action values (pause/resume/cancel) but does not map to parameter names or explain the id parameter, leaving half the semantics to 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 specific verbs (pause, resume, cancel) and resource (campaign), making the tool's purpose obvious. It does not explicitly differentiate from siblings like sendkuy_cancel_message, but the campaign scope is clear.

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?

It gives clear when-to-use guidance for pause (emergency brake when a campaign is going out wrong) and a strong warning that cancel cannot be undone. It lacks explicit when-not-to-use cases or named alternatives, but the context is sufficient.

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