Pause or Resume Campaigns

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

The description explains batch behavior (missing IDs reported in errors without failing the batch), return structure, and the fact that action values map to specific statuses. This goes beyond annotations which only indicate idempotence and non-destructiveness.

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 three sentences, front-loaded with the main purpose. Every sentence adds value without redundancy. Highly concise.

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 output schema, the description includes the return structure and explains edge cases (missing IDs). The use case is specified. It is fully complete for the tool's complexity.

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?

While the schema already describes both parameters, the description adds meaning: it explains what each action value does (maps to status) and how missing IDs are handled, which is not in 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 'Batch-change the status of up to 50 campaigns' and explains each action ('pause' sets status to 'paused', 'resume' sets to 'active'). This distinguishes it from sibling tools like campaign_create or campaign_update.

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 provides a clear use case: 'Use this for emergency pause during an incident or weekend shutoff.' It could be improved by explicitly stating when not to use or mentioning alternatives, but the context is clear.

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