List users

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

Adds rich behavior beyond annotations: includeRole may be omitted by permission, cursor resumes one prior page and never auto-paginates, permission requirement, and returns redaction-protected metadata. No contradiction with readOnlyHint or other annotations.

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?

Three dense sentences, front-loaded with the core purpose, then usage guidance, then behavioral details. Every sentence contributes unique value 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?

The description covers purpose, alternatives, permissions, pagination behavior, and return metadata (nextCursor). With an output schema present, return values need not be detailed; this description is complete for a simple list tool.

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 100%, but the description enriches parameters: includeRole behavior ('may still be omitted by permission') and cursor behavior ('resumes one prior page and this call never auto-paginates') go beyond the schema descriptions, adding valuable edge-case context.

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 and resource: 'List one Public API page of users.' It also distinguishes from sibling tool n8n_users_get by noting when to use that alternative, making the 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?

Provides explicit guidance: 'Use it for discovery; use n8n_users_get when a stable ID or exact email is known.' It also mentions the required permission, giving clear when-to-use and alternative conditions.

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