n8n MCP Server

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 effectively adds critical context: the licensing requirement (which implies access control) and the strict input format requirement ('Arguments must be provided as compact, single-line JSON'). This goes beyond the basic 'create' action, though it doesn't cover aspects like error handling or response format.

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 highly concise and front-loaded: it states the core purpose first, followed by two critical notes. Every sentence adds essential information (creation action, licensing requirement, input format), with zero wasted words, making it efficient and easy to parse.

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 complexity (a creation tool with licensing constraints), no annotations, no output schema, and low schema coverage, the description is moderately complete. It covers key behavioral aspects but lacks parameter details and output information, leaving gaps that could hinder correct tool invocation in some scenarios.

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% description coverage, and the tool description provides no information about the parameters 'clientId' and 'name'. While it mentions the JSON format requirement, it doesn't explain what these parameters represent, their expected values, or any constraints, failing to compensate for the schema's lack of documentation.

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 action ('Create a new project') and the target system ('in n8n'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'update-project' or 'delete-project' beyond the verb 'create', missing a direct comparison that would warrant a perfect score.

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 explicit prerequisites ('Requires n8n Enterprise license with project management features enabled'), which is helpful context. However, it lacks guidance on when to use this tool versus alternatives like 'update-project' or 'list-projects', and doesn't mention any exclusions or complementary tools, leaving usage context partially implied.

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