Activate workflow

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

The description adds meaningful behavioral context beyond annotations: 'this does not execute it now' clarifies the timing of effects, and 'returns target-validated active state metadata' describes the output. It also states permission requirements. This complements the annotations (destructiveHint=true, openWorldHint=true) without contradicting them, giving the agent a full picture of side effects and preconditions.

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 compact and front-loaded: the first sentence states the core purpose, and the following three sentences each deliver a distinct piece of critical guidance (ID source, deactivation alternative, permissions/output). No wasteful or redundant wording.

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 single-parameter tool with an output schema, the description covers all necessary context: what activation means, what it does not do, how to obtain the correct ID, alternative tool for reversal, required permissions, and what is returned. This is complete for an agent to safely and correctly invoke the 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?

The schema already provides a description for workflowId, but the tool description adds essential semantics: 'workflowId must be the current stable ID from n8n_workflows_list or get, not a name or version ID.' This goes beyond the schema's generic 'Stable ID of the workflow to activate' by clarifying provenance and exclusivity, significantly improving parameter understanding.

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 action: 'Activate one workflow so production triggers can accept future events'. It uses a specific verb (activate) and resource (workflow) and distinguishes itself from the sibling n8n_workflows_deactivate by explaining the effect on triggers. It also clarifies that activation does not execute the workflow immediately.

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?

Explicit when-to-use guidance is provided: 'Review the workflow first; use n8n_workflows_deactivate to stop future triggers.' It also specifies the exact source and type of workflowId ('must be the current stable ID from n8n_workflows_list or get, not a name or version ID') and prerequisites ('Requires unsafe mode plus activation permission'). This leaves no ambiguity about when or how to use the tool.

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