activate_workflow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals only the state toggle itself and omits important behavioral traits: what activation actually enables (scheduled/webhook triggers), what happens to running executions upon deactivation, reversibility, or permission requirements.

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?

A single, well-formed sentence with every word earning its place; the core toggle behavior is front-loaded and there is zero fluff. It is concise without being padded, though the brevity contributes to the under-specification noted in other dimensions.

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 tool with 100% schema coverage, the description covers the basic call shape. However, it lacks the crucial conceptual distinction between activating a workflow (enabling triggers) and executing a workflow (running once), and says nothing about effects on in-flight executions or confirmation behavior, leaving an agent to infer n8n semantics.

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%, so the baseline of 3 applies. The description adds marginal value by clarifying the 'active=false' case through the word 'deactivate,' which the schema only implies by saying 'True to activate,' but it provides no additional detail on ID format or state transition semantics.

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 pair ('activate or deactivate') with a clear resource ('workflow'), and it adds the deactivation direction that the tool name alone doesn't convey. However, it doesn't distinguish itself from siblings like update_workflow, which could also modify workflow state, or execute_workflow, which runs a workflow.

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 description provides no guidance on when to use this tool versus update_workflow or execute_workflow, no preconditions (e.g., the workflow must exist), and no exclusions. An agent cannot tell from the description whether activation means enabling triggers or something else entirely.

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