Create a user

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the description adds only the REST verb/path and tag — nothing about admin authorization requirements, what the optional flags (notify, shouldChangePassword) actually trigger, or side effects like welcome emails.

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?

It is short and front-loaded, but two of the three lines say the same thing ('Create a user' / 'Create a new user'), which is pure redundancy. Only the endpoint/tag line earns its place.

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 10-parameter admin mutation with no output schema, the description omits anything an agent needs beyond the bare verb: admin permission requirement, whether the created account is local vs OAuth, and the effect of optional fields like notify and quotaSizeInBytes. Annotations cover safety but not these operational facts.

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 100%, so the schema itself carries the 10 parameters (including required email/name/password and the avatarColor enum). The description adds no parameter meaning at all, which is the baseline 3 when the schema does the heavy lifting.

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 clear verb+resource ('Create a user' / 'Create a new user') and adds the concrete endpoint POST /admin/users with tag Users (admin), which signals this is an administrative creation path rather than self-signup. It does not explicitly contrast with siblings such as immich_sign_up_admin, so it falls short of a 5.

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 when-to-use guidance, no stated prerequisite that the caller must be an admin, and no reference to any alternative tool. The agent gets no help deciding between this and immich_sign_up_admin or immich_create_session.

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