pause_automation

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

Despite no annotations, the description covers key behaviors: queue preservation, new subscriber handling, reversibility, authentication, concurrency limits, dry-run mode, and error conditions (already paused or draft).

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?

Well-structured with front-loaded action, but some redundancy (e.g., 'Reversible' could be integrated). Still concise and clear.

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?

The description covers purpose, behavior, parameter, return value, and error conditions completely for a simple tool with one parameter and an output schema.

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 description provides an example value ('auto123') and source (list_automations) for automation_id, adding significant meaning beyond the input schema which has no description.

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 verb 'pause' and resource 'automation workflow', with additional context about preserving the queue, which distinguishes it from sibling tools like cancel_send.

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 implicitly indicates temporary use by noting reversibility and start_automation for resumption, but it does not explicitly contrast with cancel_send for permanent stopping.

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