n8n_get_user

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

The readOnlyHint annotation already signals a safe read operation, and the description adds a useful auth-related behavioral constraint: 'owner only'. This goes beyond the annotation by disclosing a permission requirement, though it does not describe error behavior or response shape.

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?

The description is a single, well-structured sentence that packs the verb, resource, lookup method, and access restriction with no wasted words. It is concise and front-loaded with the most important information.

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?

This is a simple single-parameter read tool with readOnlyHint true and clear lookup semantics. The description covers the essential details an agent needs to select and invoke it correctly: what it fetches, how to identify the user, and who is allowed to call it.

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 schema already provides 100% description coverage for the single `id` parameter ('User ID or email'). The description essentially repeats this by saying 'by ID or email', adding no new semantic detail beyond what the input schema provides.

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 ('Get'), a clear resource ('user'), the lookup key ('by ID or email'), and an access constraint ('owner only'). This clearly distinguishes it from siblings like n8n_list_users or n8n_delete_user, so an agent can immediately understand the tool's scope.

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 implies when to use the tool: for a single-user lookup by ID or email, and it adds the prerequisite that only the owner can call it. However, it does not explicitly name alternatives like n8n_list_users for listing all users or mention when not to use this tool.

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