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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context that the annotations cannot express: existing enrollments freeze in place rather than being dropped, and no new contacts enroll. It stops short of stating how the pause is reversed or what happens to in-flight sends.

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 core action is front-loaded in the first sentence and the consequence is delivered second, which is the right ordering for a mutation tool.

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?

For a two-parameter mutation with no output schema and annotations covering safety and idempotency, the description supplies the key missing piece: the effect on existing enrollments. The one real omission is reversibility (that activate_automation restores it), which an agent may need to know.

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 100% for both parameters (apiKey and automationId are both documented inline), so the schema carries the burden. The description adds no format, ID-source, or scoping detail beyond the schema, making the baseline 3 correct.

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 specific verb and resource ('Pause an automation') and immediately clarifies the operational scope. It is unambiguous, but it never names the obvious sibling pair (activate_automation to resume, or pause_campaign for the analogous campaign operation), so sibling differentiation is left to the reader.

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 guidance: nothing says when pausing is preferable to deleting an automation or to letting it run, nor what prerequisites exist. Usage is only implied by the verb itself, which is the minimum possible signal.

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