n8n: Create project

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds the license requirement, which is genuine context beyond the annotations, but says nothing about name uniqueness, what a project contains, or what happens on creation failure.

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?

Two short sentences with the action first and the constraint second; no padding. The bracketed tags are compact metadata rather than noise.

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?

For a mutating creation tool with zero schema documentation, no output schema, and an opaque `site` parameter, the definition is too thin to call reliably. It should at minimum define the two required inputs and clarify what a created project looks like.

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% across both required parameters, so the description must carry the burden and it does not. The `site` parameter in particular is ambiguous — whether it expects a site ID, slug, or URL is entirely undocumented, which risks a failed call.

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?

States a specific verb and resource ("Create a new project") plus an enterprise-only scope marker. It is clear what the tool does, but it does not differentiate itself from the several other create_project siblings in the catalog (coolify, openpanel), leaving the agent to rely on the n8n prefix alone.

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?

Provides a real prerequisite ("Requires n8n Enterprise/Pro license"), which is useful gating information. However, it gives no guidance on when to choose this over other project-creation tools or what to do if the license check fails.

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