Start a campaign

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

Annotations already declare read-only, open-world, idempotent, and non-destructive hints, but the description adds important behavior: instant campaigns send to all eligible contacts, spend real credit, and can fail with insufficient_credits. It also explains scheduled/recurring waiting behavior and a human notification requirement.

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 front-loaded with purpose, then adds key behavior, a human-confirmation instruction, and the relevant alternative. Every sentence contributes useful information with no redundancy.

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 the available annotations, output schema, and single fully documented parameter, the description covers the critical operational details: cost, refusal mode, instant vs scheduled behavior, and the pause/cancel alternative. Nothing essential for correct invocation is missing.

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 the single id parameter is already documented as the campaign id in cmp_... format. The description does not add parameter-specific guidance beyond the schema, making the baseline score appropriate.

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?

States a specific verb and resource: starting a draft or scheduled campaign. It distinguishes instant, scheduled, and recurring campaign behavior, so an agent can understand exactly what this tool does without opening the schema.

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?

Clearly indicates the main use case and names sendkuy_control_campaign as the alternative for pausing or cancelling. It also includes a human-confirmation rule, though it does not explicitly discuss inspecting a campaign first with get_campaign.

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