Activate a workflow

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

With no annotations, the description must carry the behavioral burden. It states the outcome (triggers start listening) but does not disclose potential side effects, idempotency, or whether the workflow must currently be inactive. The behavior is minimal but not misleading.

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 a single compact sentence that immediately states the action and effect, with no filler or redundant information. It is optimally concise.

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 simple one-parameter activation tool with no output schema, this description provides essential context for an agent to select and invoke it correctly. It lacks details on prerequisites or response format, but those are not critical for this tool's simplicity.

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 has one required 'id' parameter with 0% coverage, and the description does not explicitly explain that the id is for the workflow, though it is implied by the tool name. The description adds no parameter-level meaning beyond what the schema already shows.

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 uses a specific verb (activate) and resource (workflow) and adds a clear effect ('so its triggers start listening'), distinguishing it from the sibling n8n_deactivate_workflow. The purpose is unambiguous.

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?

The implied usage is when you want to publish a workflow and enable its triggers, but the description does not explicitly state when to use this tool versus alternatives like n8n_update_workflow or n8n_validate_workflow. No exclusions or prerequisites are mentioned.

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