create_workflow

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write nature is conveyed. The description adds the 'Optionally activate immediately' behavior, which is a useful extra context. However, it does not disclose other behavioral traits such as permissions needed, return value, or side effects beyond creation, so it stays at a baseline level.

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 two sentences, front-loaded with the primary action, and contains no fluff. Every phrase adds meaning, including the optional activation note.

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 tool has 6 parameters, nested objects, and no output schema, the description provides only a high-level overview. It does not mention what is returned or any error conditions. However, the schema carries the burden for parameters, so the description is minimally adequate but leaves gaps regarding expected output and usage 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?

Schema description coverage is 100%, so the baseline is 3. The description itself does not add parameter-level meaning beyond what the schema already provides (e.g., the schema explains connections format and references list_common_nodes). The description's mention of 'nodes, connections, and settings' is redundant with parameter names, so no additional value is added.

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 'Create' and the resource 'n8n workflow', specifying that it includes nodes, connections, and settings. It also mentions optional activation, which distinguishes it from related tools like update_workflow or duplicate_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 implies usage when creating a new workflow but does not explicitly state when to use this tool versus alternatives like update_workflow or import_workflow. There is no exclusionary language or reference to sibling tools, so it meets only the 'implied usage' threshold.

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