Pause a running campaign

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

No annotations are provided, so the description carries the full burden. It only states the action is reversible, but lacks details on side effects, state changes, or timing. For a mutation tool, more transparency about what happens when paused is needed.

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 very short with two sentences, front-loading the purpose. It is concise but could be slightly more structured. Every sentence adds value, though it may be too brief.

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 no annotations, no output schema, and only two parameters, the description is minimal. It fails to specify what happens to campaign delivery, whether pause is immediate, or any prerequisites. It is incomplete for an agent to fully understand the tool's behavior.

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?

The schema has two parameters (id required, reason optional) with 0% description coverage. The tool description does not explain any parameter meanings, defaults, or usage. It adds no value 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 clearly states the tool pauses a scheduled or running campaign. It uses the verb 'Pause' with the resource 'campaign'. However, it does not explicitly distinguish from siblings like campaign_archive or campaign_complete, though it mentions reversibility via campaign_resume, which hints at differentiation.

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 indicates use for scheduled or running campaigns and mentions reversibility via campaign_resume. It implies when to use but does not explicitly state when not to use or provide alternatives beyond the sibling. No exclusions are given.

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