Set Campaign Status

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: starting is an outward-facing, real-people action gated by confirm=true, while pausing is reversible/safe. It stops short of covering archival permanence, permissions, or rate limits.

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?

Front-loaded with the capability, then the enum values, then the safety distinction. Four short lines, no filler; the safety sentence directly justifies its length.

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?

An output schema exists so return values need not be described, and the mutation's safety profile is partially covered. The main residual gap is whether archiving is irreversible and what happens to a running campaign's in-flight work.

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 0%, so the description must compensate, and it does for the two non-obvious parameters: it enumerates valid status values (active, paused, archived) and explains what confirm controls and when it is required. campaign_id is left unexplained but is self-evident.

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 set (start, pause, archive) on a specific resource (campaign), which cleanly separates it from siblings like create_campaign, list_campaigns and get_campaign_stats.

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?

Gives clear operational guidance: pausing is safe, starting requires confirm=true because it reaches real people. It does not name alternative tools, but the when-to-use distinction between the three statuses is explicit.

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