n8n_list_users

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

The readOnlyHint annotation already signals a safe read operation, and the description adds a useful behavioral/access restriction: the operation is owner-only and lists all users rather than a filtered subset. No contradiction with the annotation.

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 short, front-loaded sentence: 'List all users (owner only).' Every word contributes either the action, the resource, or an important constraint, with no filler or redundancy.

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 simple, read-only list operation with one optional boolean parameter fully documented in the schema, this description is complete. An agent knows what the tool does, who can use it, what its scope is, and that it is non-mutating.

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 schema covers the only parameter (includeRole) with a clear description ('Include role information'), so baseline is 3. The tool description does not add any further parameter context, but it does not need to given 100% schema coverage.

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 uses a specific verb ('List') and resource ('all users'), and adds a clear scoping restriction ('owner only'). This clearly distinguishes it from n8n_get_user (single user) and from the many workflow/credential/tag list tools among its siblings.

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 does not explicitly state when to choose this tool over alternatives like n8n_get_user, nor does it provide when-not-to-use guidance. The usage is implied by the name and phrasing, but there is no explicit routing to alternatives or exclusions.

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