n8n_delete_user

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

No annotations are provided, so the description carries the full burden. While 'Delete' implies a destructive operation, the description fails to disclose whether deletion is permanent, whether user data/workflows are cascaded or reassigned, or if the operation is reversible.

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 extremely brief (one sentence plus a tag), but this brevity comes at the cost of essential information. While not verbose, it suffers from under-specification rather than effective conciseness given the destructive nature of the operation.

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 like user deletion, the description is inadequate. It fails to explain consequences (what happens to owned workflows, credentials, executions), required authorization levels, or return values, leaving critical gaps despite the lack of output schema.

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% (neither 'site' nor 'user_id' have descriptions), yet the description provides no compensation. It does not clarify what format 'user_id' expects (UUID, email, username) or what 'site' refers to, leaving both parameters effectively undocumented.

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 basic action (Delete) and resource (user from the instance), but fails to distinguish from the sibling tool 'n8n_remove_project_user', which removes a user from a project rather than deleting the account entirely. The '[UNIFIED]' prefix adds no semantic value.

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?

No guidance provided on when to use this tool versus alternatives like 'n8n_remove_project_user' or 'n8n_change_user_role'. No mention of required permissions (admin rights) or prerequisites for deletion.

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