n8n_get_user

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states the retrieval action but fails to disclose error behavior (e.g., user not found), whether the operation is read-only safe, rate limits, or what specific 'details' are returned.

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?

Extremely concise single sentence. However, the '[UNIFIED]' prefix appears to be internal metadata noise that does not aid agent understanding, slightly detracting from an otherwise efficient structure.

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 zero schema descriptions, no annotations, and no output schema, the description is insufficient. Critical gaps remain around the 'site' parameter semantics, the effect of 'include_role', and the shape of the returned user details.

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 0%, requiring the description to compensate. It partially explains 'user_id' (accepts ID or email) but completely omits explanation for required 'site' parameter (format, expected values) and 'include_role' boolean (what additional data this includes).

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?

Clear verb 'Get' and resource 'user details' with specific lookup identifiers 'by ID or email'. However, it does not explicitly differentiate from sibling n8n_list_users or clarify when to use this specific lookup versus searching.

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?

No guidance provided on when to use this tool versus n8n_list_users or other user-related operations. No mention of prerequisites like authentication or required permissions.

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