campaigns_resume

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

No annotations are provided, so the description carries full responsibility. It discloses the state change but does not specify behavior if the campaign is not paused, required permissions, error conditions, or side effects. This is minimal for a mutation tool.

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 a single, front-loaded sentence with no redundancies. Every word serves a purpose, making it exceptionally concise and well-structured.

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 tool's simplicity (one parameter, output schema present), the description is minimally adequate. However, it lacks guidance on when to use resume versus start, what constitutes a valid paused campaign, and any operational constraints. It is incomplete but not critically so.

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 input schema has one required string campaign_id with no description (0% coverage). The tool description does not mention the parameter or provide format/source details, so it adds little value beyond the field name. The context from the tool name and description is weak.

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 uses a specific verb 'Resume' with a clear resource 'paused campaign', making the tool's purpose distinct from siblings like campaigns_pause, campaigns_start, or campaigns_stop. It clearly indicates the action and state transition.

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?

There is no explicit when-to-use or alternatives, but the phrase 'paused campaign' implies it should be used when a campaign is already paused. However, it does not mention related tools like campaigns_start or explain the difference between resuming and starting.

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