n8n: Delete project

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds the license/availability requirement, which is genuinely new information, but says nothing about cascade effects (do workflows, credentials or memberships survive?) or irreversibility, which is the key unknown for a destructive operation.

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, front-loaded sentences with the action first and the license constraint second. The [UNIFIED]/[Enterprise] tags are slightly noisy but cost almost nothing and do convey licensing context.

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 destructive, non-idempotent mutation with two undocumented required parameters and no output schema, the description is too thin. It omits what is destroyed beyond the project record, whether the action is recoverable, and any failure conditions, so an agent cannot call it confidently.

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% for both parameters, so the description carries full responsibility and provides nothing. It never explains what 'site' denotes (the n8n instance/tenant) or the expected form of 'project_id', leaving an agent to guess at both required values.

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 ('Delete a project'), which unambiguously separates it from n8n_get_project, n8n_update_project and n8n_create_project. The bracketed tags [UNIFIED] and [Enterprise] add context but no additional purpose detail, so it stops short of a 5.

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 supplies one real prerequisite — an n8n Enterprise/Pro license — which an agent needs before invoking. It gives no guidance on alternatives (e.g., update_project or remove_project_user) or on conditions such as whether the project must be empty first, so usage is only partially framed.

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