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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the bar is lower. The description adds real behavioral context beyond them: the concrete consequence of enabling (the connected account answers triggers automatically) and of disabling (the bot stops answering immediately), plus a confirmation guardrail.

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?

Purpose is front-loaded in the first sentence, with effect and guardrail following. The middle sentence is long and clause-heavy, but no sentence is wasted.

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 strong annotations and no output schema, the description covers the essential effect, the safety guardrail, and the disable outcome. It omits any indication of the response payload, but with no output schema that is a minor gap.

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 only 33% – only idempotencyKey is documented in the schema, while flowId and active carry no description. The description implies the active toggle's meaning ('enabling makes the connected account answer automatically'), but never clarifies what flowId refers to or its format, so it only partially compensates.

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 pair (enable/disable) and a precise resource (an automation flow), which cleanly separates it from sibling toggles like activate_sequence, activate_autopilot_plan, and set_coupon_active. An agent can tell what it does and which resource it acts on without opening the schema.

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?

Gives an explicit prerequisite/alternative: 'review it with preview_automation and confirm with the user first', and describes the disable side-effect ('stops the bot answering... immediately'). It does not, however, say when to prefer this over update_automation or other activation tools, so the routing guidance is partial.

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