Retrieve a user

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the underlying REST operation (GET /admin/users/{id}) and tag, which is mild extra context but discloses nothing about error behavior or permissions.

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 body is short, but the first line 'Retrieve a user' simply duplicates the title, and the second sentence repeats the same idea ('Retrieve a specific user by their ID'). The operation/tag footer is useful metadata, but roughly half the text is redundant.

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 single-parameter read tool with full annotation coverage and no output schema, the description is nearly sufficient: verb, resource, ID-based lookup, and the admin endpoint are all present. The one real gap is the absence of routing guidance among the many user-retrieval siblings.

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% (the single 'id' parameter is documented as uuid format), so the schema already carries the parameter burden. The phrase 'by their ID' restates the schema rather than adding format, validation, or source-of-ID guidance, so the baseline 3 applies.

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 specific user by their ID') and the admin tag plus the GET /admin/users/{id} operation line make the admin scope explicit. However, it never distinguishes itself from the close siblings immich_get_user, immich_get_my_user, or immich_search_users_admin, so an agent must infer which retrieval variant applies.

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 when-to-use or when-not-to-use guidance. The 'admin' tag and endpoint path imply an administrative context, but the description does not tell the agent to prefer this over immich_get_user for self-lookup or immich_search_users_admin for lookup by other criteria.

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