n8n: Change user role

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not say what permissions are required, what effect the change has on the user's existing access, or whether the change 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?

A single short sentence with no filler, so nothing is wasted, but the brevity comes at the cost of substance rather than being achieved through efficient density. The '[UNIFIED]' prefix carries no meaning for an agent.

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 mutation with no output schema and zero schema description coverage, the definition should at minimum define acceptable role values and the identity format. Nearly everything an agent needs to invoke it correctly is missing.

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%, so the description carries the full burden for three required parameters and does not deliver. Most critically, the valid values for new_role are never enumerated, and the expected format for user_id (ID vs email) and the meaning of site are unexplained.

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 and resource ('Change a user's global role') and the word 'global' is the only thing distinguishing it from the sibling n8n_change_project_user_role, but that distinction is never made explicit. An agent must infer the contrast from the sibling name rather than reading it here.

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 statement of when to use this tool versus n8n_change_project_user_role or other user tools, nor any prerequisite or caution. The only guidance is implicit in the word 'global'.

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