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 describes the validation process and output report, adding useful context beyond basic creation. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a mutation tool with complex behavior.

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 front-loaded with key actions and outcomes in three efficient sentences. Each sentence adds value: creation with validation, output details, and prerequisites. It avoids redundancy but could be slightly more structured for readability.

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's complexity (5 parameters, nested objects, no annotations) and the presence of an output schema, the description covers core functionality and output but lacks details on parameter semantics and behavioral nuances. It is minimally adequate but has clear gaps in 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 0%, so the description must compensate for undocumented parameters. It only mentions 'test_data' explicitly, leaving 'name', 'nodes', 'connections', and 'settings' unexplained. This adds minimal value beyond the schema, failing to adequately clarify parameter meanings.

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 tool creates a workflow with automatic double-validation, specifying the validation steps (structural check, two execution passes, consistency comparison) and the output (PASS/FAIL report). It distinguishes from sibling 'create_workflow' by emphasizing validation, making the purpose specific and differentiated.

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 clear context for usage: it requires 'write_mode' and 'test_data for meaningful functional testing', indicating prerequisites. However, it does not explicitly state when to use this tool versus alternatives like 'create_workflow' or 'execute_workflow', missing explicit sibling differentiation.

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