Delete user

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

Beyond the destructiveHint annotation, the description discloses permanent deletion, the non-acceptance of email addresses, lack of a transfer target, required unsafe mode and permission, and the absence of a rollback claim. These are critical behavioral details not present in the annotations.

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 four concise sentences, with the main purpose front-loaded. Every sentence earns its place by providing either a prerequisite, an identity constraint, a verification step, or a behavioral consequence—no filler or repetition.

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?

Given a single parameter, rich annotations, and an output schema, the description fully covers prerequisites, ID sourcing, verification, permission requirements, and return behavior. It leaves no significant ambiguity about how to invoke the tool correctly.

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?

Although the schema provides a stable ID description with a pattern, the description adds crucial semantics: the userId must come from n8n_users_list or get, and an email address is not accepted. This prevents a common misuse and goes well beyond the schema's baseline.

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 opens with 'Permanently delete one API-eligible user,' using a specific verb and resource while distinguishing this from sibling delete tools. It further clarifies the identity requirement (stable ID, not email), making the tool's purpose unmistakable.

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?

It explicitly instructs the agent to obtain userId from n8n_users_list or get and to verify the target with get first. It also states required permissions (unsafe mode, user-delete permission) and implies when not to use it by noting there is no transfer target and no rollback claim.

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