Read a Neo4j Community user

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

The annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful domain fact — that every Community user has full administrative privileges — which tells the agent the returned identity is always privileged. It does not say what happens for a nonexistent user or what the response contains.

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?

Two short sentences, front-loaded with the operation and followed by the one piece of context worth stating. Nothing is padded, though the second sentence could be tied more explicitly to why an agent should care.

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 three-parameter lookup with no output schema and zero parameter descriptions, the definition leaves too much unsaid: it never explains the cluster/namespace scoping, the identifier format for 'user', or what a successful read returns. The privilege note is helpful but does not fill those gaps.

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 0% for the top-level parameters: 'cluster' (with a strict lowercase pattern) and 'user' carry no descriptions, and the description adds no meaning for either. Only 'namespace' is documented, via the referenced NamespaceName definition, so the description fails to compensate for the coverage 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 description states a specific verb and resource: 'Read a Neo4j Community user.' That is enough to distinguish it from the plural sibling neo4j_users_list, though the singular/plural split is left implicit rather than named. It does not mention the cluster or namespace scoping that the schema requires.

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 use this tool versus neo4j_users_list, database_user_get, or other per-backend user getters in the sibling set. Usage is only inferable from the verb 'Read' plus the singular resource name, and no prerequisites or exclusions are stated.

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