List users

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

No annotations are provided, so the description carries full burden. It discloses the role requirement but lacks details about pagination, rate limits, or authentication scope. The output schema exists but the description does not add behavioral context beyond what schema covers.

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 sentence that conveys the core purpose and a key constraint (role). It is not verbose, but could be slightly more structured to include parameter hints or pagination note while remaining concise.

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 that there are 3 parameters (limit, cursor, includeRole) and no annotations, the description is insufficient. It omits pagination behavior, response structure hints, and how to use the cursor for pagination. The output schema exists but the description does not complement it.

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 only 33% (only includeRole has a description). The description does not explain any parameters, such as limit (pagination) or cursor (pagination mechanism). It adds no value beyond the sparse schema documentation.

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 clearly states 'List all users in the n8n instance', which specifies the verb (list) and resource (all users). It also adds the owner role requirement, differentiating it from tools like n8n_get_user that retrieve a single user.

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 mentions the required role ('owner') which is a prerequisite for use, but does not provide guidance on when to use this tool versus alternatives like n8n_get_user or when not to use it. No comparisons to sibling tools are given.

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