n8n-mcp

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 mentions the write_mode requirement, which is useful context about permissions/configuration. However, it doesn't describe what happens after creation (e.g., whether the workflow is active, what the response contains), potential side effects, error conditions, or rate limits. For a creation tool with zero annotation coverage, this leaves significant gaps.

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 at just two sentences, with zero wasted words. The first sentence states the core purpose, and the second adds the only contextual requirement. It's perfectly front-loaded and appropriately sized for the information it conveys.

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 that there's an output schema (which handles return values), the description doesn't need to explain response format. However, for a creation tool with 4 parameters (3 required), nested objects, and no annotations, the description is incomplete. It mentions the write_mode requirement but doesn't help the agent understand what constitutes a valid workflow or how to structure the complex 'nodes' and 'connections' parameters.

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 0%, meaning none of the 4 parameters have descriptions in the schema. The tool description provides no information about what 'name', 'nodes', 'connections', or 'settings' should contain, their formats, constraints, or examples. This leaves the agent guessing about parameter meanings and requirements, which is inadequate given the low schema coverage.

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 resource 'new workflow', making the purpose immediately understandable. It distinguishes from siblings like 'update_workflow' by focusing on creation rather than modification. However, it doesn't specify what a workflow consists of or its domain context.

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 one explicit usage condition: 'Requires write_mode to be enabled.' This gives important context about prerequisites. However, it doesn't explain when to use this tool versus alternatives like 'create_and_validate_workflow' or 'update_workflow', nor does it mention any exclusions or complementary tools.

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