n8n_create_user

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

No annotations are provided, so the description carries full burden. It fails to disclose whether the operation sends invitation emails, requires confirmation, what default permissions are assigned, or what error conditions to expect. 'Invite/create' suggests two possible behaviors but doesn't clarify which occurs when.

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 brief (one sentence), but the '[UNIFIED]' prefix wastes valuable space without adding semantic value for the agent. The dual verb 'Invite/create' creates ambiguity that could have been clarified with additional words.

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 user creation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It lacks critical context about site scoping, available roles, invitation workflows, and return values.

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 coverage is 0% (no parameter descriptions in JSON), yet the description provides no compensation. It doesn't explain what 'site' refers to (instance URL? project ID?), valid 'role' values (only default is shown), or email format requirements. All 3 parameters remain 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 ('Invite/create a new user') but is ambiguous about whether this sends an invitation email or directly creates a user. The '[UNIFIED]' prefix appears to be internal metadata noise that doesn't help the agent. It does not distinguish from siblings like 'n8n_add_project_users' (adds to project) vs this tool (global user creation).

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 vs alternatives like 'n8n_add_project_users' for existing users, or when invitation vs direct creation occurs. No prerequisites (e.g., admin permissions) are mentioned despite sibling tools existing for user management.

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