n8n_delete_project

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

The description merely states 'Delete a project' and adds nothing beyond the destructiveHint annotation. It does not disclose irreversibility, cascading effects on associated workflows or credentials, or permission requirements, so an agent has no behavioral detail beyond the structured hint.

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 a single, focused sentence with no filler or repetition, which is structurally clean. However, it is so terse that it contributes almost no information beyond the tool name, so it is efficient but not richly written.

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 one-parameter, destructive operation with no output schema, the bare description plus input schema is minimally workable: an agent can infer the call shape. It lacks usage guidance and any statement of consequences or required permissions, so it is not fully complete.

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 schema description covers the only parameter at 100% ('Project ID to delete'), so the description does not need to explain it. The tool description adds no extra parameter semantics, but the schema's coverage supports the baseline score.

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 names a specific verb ('Delete') and resource ('project'), which is unambiguous and distinguishes it from sibling delete operations on workflows, credentials, executions, tags, variables, and users. It is clear, though it adds no detail beyond what the tool's name already conveys.

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?

There is no guidance about when to call this tool instead of e.g. n8n_update_project or n8n_list_projects, nor any prerequisites or alternatives. The only usage signal is the required id parameter in the schema, which is not guidance in the description.

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