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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the safety profile is covered by structured data. The description adds nothing behavioral beyond that: it does not say whether pausing halts in-flight runs, whether the change is reversible, or what permissions are needed. Minimum viable given annotation coverage.

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?

Two short sentences with zero filler; the usage trigger is front-loaded and the prerequisite id source follows. Every clause earns its place.

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?

With an output schema present, return values need no explanation, and both parameters are fully documented in the schema. The only gap is the effect of pausing on the automation's behavior, which the annotations partially cover via the mutation hints. Otherwise complete for a simple two-parameter toggle.

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% and both parameters are fully documented there ('id' from list_automations or create_automation; 'enabled' false=pause, true=resume). The description only reiterates the id dependency, adding no format or semantic detail the schema lacks, so the baseline 3 applies.

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 states a concrete action on a concrete resource ('pause one of their automations or turn a paused one back on'), so an agent can tell it is a state-toggle tool rather than a creation or listing tool. It does not explicitly contrast itself with siblings like create_automation or list_automations, but the name and phrasing are distinct enough to avoid confusion.

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?

It gives an explicit trigger condition ('Use this when the user wants to pause... or turn a paused one back on') and names the prerequisite tool for obtaining the id (list_automations). It stops short of stating when NOT to use it, or which tool handles other automation edits, so it falls just below a full 5.

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