activate_workflow

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Activate' without explaining side effects (e.g., does it change workflow state, start execution, require specific permissions?). The lack of details on outcomes or requirements undermines safe and correct invocation.

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 extremely concise (one sentence), which is efficient but at the cost of essential information. For a simple tool, brevity is acceptable, but the lack of structure (no front-loading of critical context) reduces its utility. The sentence is clear but not sufficiently informative.

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?

Given the single parameter, no output schema, and no annotations, the description is incomplete. It fails to clarify the tool's behavior, return value, or idempotency. The agent cannot reliably predict the outcome or handle errors without additional context.

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 input schema has 0% coverage and the description adds no explanation for the single required parameter 'id'. The agent receives no hint about what 'id' represents (e.g., workflow ID) or what value format is expected. This is a critical gap for proper tool usage.

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 verb 'Activate' and the resource 'n8n workflow', establishing the basic action. However, it does not specify what activation entails conceptually (e.g., enabling vs. triggering), and the sibling tool 'deactivate_workflow' provides the only context. The description lacks a verb+resource scope that differentiates it from potential other workflow manipulations.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or situations where activation is appropriate. The agent is left to infer from the tool name alone, which is insufficient for reliable selection.

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