n8n_delete_project

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

No annotations are provided, so the description carries full burden. While 'Delete' implies destruction, the description fails to disclose cascading effects (what happens to workflows/executions in the project), reversibility, or specific auth requirements beyond the license.

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 appropriately brief with two information-dense sentences. The '[UNIFIED] [Enterprise]' prefix is structural metadata noise, but the core content is well-structured and front-loaded with the action.

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 operation with no output schema and zero parameter documentation, the description is insufficient. It mentions the license requirement but omits expected return values, error conditions, and the scope of data deletion.

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 'site' and 'project_id'. The description adds no semantic context to compensate—it's unclear if 'site' refers to a URL, domain, or instance name, or what format 'project_id' expects.

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 states the specific action (Delete) and resource (project) clearly. The '[Enterprise]' tag helps distinguish this from standard operations, and the verb distinguishes it from siblings like n8n_create_project and n8n_update_project.

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 a critical prerequisite (Requires n8n Enterprise/Pro license) which constrains when the tool can be used. However, it lacks explicit guidance on when NOT to use it or pointers to alternatives like n8n_update_project.

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