List Neo4j Community users

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

Beyond the read-only and non-destructive annotations, the description discloses that Community users have full administrative privileges and that the managed neo4j administrator is omitted. These are useful security and result-visibility details, although other read behavior such as result formatting is not described.

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 short sentences front-load the operation and then add the privilege and visibility caveats without filler. The wording is easy to scan and appropriately sized for a simple list tool.

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 purpose, privilege implications, and an important result exclusion are covered, while annotations establish safe-read behavior. Missing cluster/namespace targeting semantics and limited information about the returned representation leave avoidable gaps, particularly because there is no output schema.

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 description never explains cluster or namespace, how namespace affects the listing, or what happens when the optional namespace is omitted. With reported 0% schema description coverage, it adds no parameter meaning and does not compensate for the documentation gap.

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 opening line states a specific verb and resource: listing Neo4j Community users. It clearly conveys the basic operation, but does not explicitly differentiate this tool from neo4j_user_get or the broader database_users_list.

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?

There is no explicit guidance on when to enumerate users, when to retrieve a single user instead, or how this tool differs from database_users_list. The hidden-administrator note limits the expected results but does not provide meaningful tool-selection guidance.

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