update_automation

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

With no annotations provided, the description carries the burden of disclosing behavior. It explains the pause/unpause mechanics and field replacement semantics, but does not mention potential side effects, permission requirements, or state-dependent behavior (e.g., whether an already paused automation can be paused again).

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 well-structured with a clear main purpose, mode-specific instructions, and a compact arg list. Each sentence adds value, and the front-loaded summary makes it easy to scan quickly.

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 tool has 10 parameters and no annotations or output schema. The description covers all parameters and mode usage, but lacks information about edge cases like invalid state transitions or error conditions. Overall, it is fairly complete for a complex mutation tool.

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 must compensate. It provides explanations for all 10 parameters, including specific values for action, the replacement behavior for slideshow_hooks, and the meaning of each update field. This fully compensates for the schema's lack of descriptions.

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 tool updates automation settings or pauses/unpauses it, using a specific verb and resource. It distinguishes itself from sibling tools like get_automation, delete_automation, and run_automation by focusing on update and pause/unpause operations.

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 explicitly explains when to use action with 'pause' or 'unpause' and when to update config fields, including the mutual exclusivity of action. It does not explicitly mention alternatives, but the internal mode guidance is clear and sufficient.

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