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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds concrete downstream effects the annotations cannot convey: contacts start being enrolled by matching triggers and emails can go out immediately. That is meaningful behavioral context beyond the structured hints, though the response/return behavior is not described.

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?

Three short sentences, front-loaded with the action, then the effect, then the caution. Each sentence contributes distinct information and nothing is padding.

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, the description covers the action, its side effects, and a safety caution, which is most of what an agent needs. It does not mention behavior when the automation is already active or what the call returns, leaving minor gaps.

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 (automationId, apiKey override), so the schema already carries parameter meaning. The description adds nothing about parameter format or which ID to supply, 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?

States a specific verb+resource ('Activate an automation') and immediately explains the operational consequence: new events matching its triggers begin enrolling contacts. That distinguishes it clearly from pause_automation and enroll_in_automation without needing to name them.

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?

Provides an explicit precondition ('Confirm with the user first'), which is real usage guidance for a state-changing tool. It does not, however, contrast with alternatives such as pause_automation or explain when activation is inappropriate, so it falls short of the 5 tier.

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