Get all users

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful scope detail that it returns ALL users rather than a filtered subset, but says nothing about pagination, admin-only access, or result size for what is an openWorld read.

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 first line merely repeats the title and the second sentence restates the first ('Get all users' / 'Retrieve a list of all users'), which is redundant. Only the trailing 'Immich operation: GET /users' line adds new information, so the definition carries waste for its short length.

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 zero-parameter read tool whose annotations cover the safety profile, the core need is met. Still, with no output schema the description could indicate the shape of the returned user list or any admin restriction, and it omits both.

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 tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies for a no-parameter tool.

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 ('Retrieve a list of all users on the server'), making the operation unambiguous. However, it does not differentiate this tool from close siblings such as immich_search_users_admin, immich_get_user, or immich_get_my_user, and the name's 'search' framing is at odds with the parameterless 'get all' behavior.

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 guidance on when to use this tool versus immich_search_users_admin (which presumably filters) or immich_get_my_user. No prerequisites, permission requirements, or exclusions are mentioned.

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