n8n_list_users

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It identifies the operation as a list, but fails to mention pagination behavior (despite having `cursor` and `limit` parameters), read-only safety, or return format. Minimal disclosure for a data retrieval tool.

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?

While brief, the description contains only two sentences where the second ('All parameters are OPTIONAL') is factually incorrect per the schema. The '[UNIFIED]' tag wastes space. The structure is poor because the single parameter-related statement is misleading.

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 tool with 4 parameters, 0% schema coverage, no output schema, and no annotations, the description is inadequate. It lacks explanation of pagination, filtering capabilities, or the response structure, leaving the agent with insufficient context to use the tool effectively.

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?

With 0% schema description coverage, the description completely fails to compensate. It does not explain what `site` represents (n8n instance identifier?), the pagination mechanism (`cursor`/`limit`), or the purpose of `include_role`. The false claim about optionality further damages understanding of the required `site` parameter.

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 the tool 'List[s] all users in the n8n instance' with a specific verb and resource. However, the '[UNIFIED]' prefix adds noise without value, and the description does not explicitly differentiate this from the sibling `n8n_get_user` tool.

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 falsely claims 'All parameters are OPTIONAL,' which contradicts the input schema where `site` is listed as required. This is misleading guidance that could cause invocation errors. It also provides no guidance on when to use this listing tool versus the singular `n8n_get_user`.

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