Pause or Resume Campaigns

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

Annotations already indicate idempotentHint=true, and non-destructive. Description adds important behavior: batch status change, partial failure handling (errors array but not fail whole batch). This goes beyond annotations. However, could mention that pausing an already paused campaign is idempotent (redundant given idempotentHint but still good for clarity).

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?

Three sentences, front-loaded with key action and limits, then specific parameter behavior, then return format and use case. No filler, every sentence adds value.

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 modest complexity (2 params, no output schema), description sufficiently covers behavior, partial failure, and use case. Return format is described adequately. Could mention the structure of the 'errors' array for completeness, but overall complete enough for safe call.

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 100% (both params documented). Description adds mapping: action='pause' → status='paused'; action='resume' → status='active'. Also mentions that missing campaign_ids are reported in errors, adding semantic meaning beyond 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?

Description uses specific verb-resource pair ('Pause or Resume Campaigns') and explicitly states the batch nature (up to 50 campaigns) and the effect of each action. This clearly distinguishes it from siblings 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?

Describes explicit use cases: 'emergency pause during an incident or weekend shutoff'. Also explains that missing IDs are reported without failing the batch, which guides appropriate usage. No exclusions or alternatives mentioned, but use case is clear enough.

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