n8n_create_users

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

With no annotations, the description carries the full burden of disclosing behavior, but it only repeats the core operation. It does not explain permissions required, failure semantics for partially invalid batches, duplicate email handling, idempotency, or what happens after creation.

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 a single, front-loaded sentence with no filler or redundant detail. Every word contributes to identifying the tool's function.

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?

This is a bulk mutation tool with no output schema and no annotations, yet the description does not mention return behavior, error conditions, permission requirements, or whether creation is all-or-nothing. An agent has enough schema information to build the request body but not enough contextual information to anticipate tool behavior or handle failures 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?

The input schema already documents the 'users' array and each user object field, including required 'email' and the role enum (global:owner, global:admin, global:member). The description adds no parameter-level meaning beyond what the schema provides, so the schema-coverage baseline of 3 applies.

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 a specific action ('Create') and a specific resource ('multiple users'), which clearly identifies what the tool does. The bulk nature ('at once') and the contrast with sibling tools like n8n_list_users, n8n_get_user, and n8n_delete_user make its purpose unambiguous.

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 implies the tool is for creating users, but it provides no explicit guidance on when to prefer it over alternatives or when not to use it. There is no mention of conditions, prerequisites, or exclusions, so usage context is only implicit.

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