n8n: Update project

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is known from structured data. The description does add genuinely useful non-schema context, namely that the operation is gated behind an Enterprise/Pro license. What it does not add is the consequence of the destructiveness (e.g. whether renaming breaks references, whether fields not supplied are preserved).

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 license constraint front-loaded after the bracketed tags. Efficient and readable, though the [UNIFIED]/[Enterprise] prefixes duplicate information stated again in the body.

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?

This is a destructive mutation with zero schema description coverage and no output schema, so the description carries the whole burden of explaining the required identifiers and the effect of a rename. It supplies only the license gate, leaving an agent without enough information to call it confidently beyond guessing at parameter values.

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% and none of the three parameters (site, project_id, name) are explained or exemplified in the description. The word "metadata" loosely hints that name is the mutated field, but site and project_id, which are required to address the target project, are left entirely to inference.

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 ("Update project metadata") and pins the vendor scope with the n8n/Enterprise tags, which separates it from the coolify_/openpanel_ update_project siblings. It is slightly imprecise, though: the schema shows only a name field plus identifiers, so "metadata" is broader than what the call can actually change.

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 only guidance is a license prerequisite (Enterprise/Pro). There is no statement of when to call this versus n8n_get_project, n8n_create_project, or n8n_transfer_workflow_to_project, and no exclusions or preconditions beyond licensing.

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