pause_campaign

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

With no annotations provided, the description must carry the behavioral burden. 'HIGH_WRITE' at least signals a high-impact mutation, but the description does not explain what pausing does to the campaign, whether it is reversible, or whether confirmation is required. This leaves significant behavioral ambiguity.

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 extremely short and front-loaded: one purpose sentence and one warning label. No filler words exist, though 'Pause/stop' is somewhat redundant and the overall description is terse to the point of under-specifying.

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 mutateive nature and lck of annotations or output schema, the description is not complete. It does not clarify the confirm parameter, the campaign state transition, reversibility, or any consequences of the high-write action. An agent would still nave to guess at important invocation details.

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 0%, so the description needed to compensate. The campaign_id parameter is reasonably inferable from the name, but the confirm parameter is not explained at all — an agent cannot tell whether confirm=true is mandatory, what it confirms, or what happens if false. The description adds no parameter-level meaning.

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 a specific verb ('Pause/stop') and resource ('campaign'), so an agent knows what the tool does. It does not explicitly contrast itself with sibling tools like launch_campaign or update_campaign, but the action name itself is distinct enough.

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?

No guidance is given about when to use this tool versus alternatives such as launch_campaign or update_campaign. There is also no mention of prerequisites, side effects, or situations where pausing is appropriate vs. stopping entirely.

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