Update user role

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds only the endpoint shape, which is consistent with idempotent PUT semantics, but says nothing about required album-owner permissions, whether demoting an owner has side effects, or reversibility.

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?

Two short sentences, front-loaded with the action, plus a compact operation/tag line. Efficient and readable, though the title/description repetition of 'Update user role' and 'Change the role' is mildly 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 3-parameter, fully-documented, non-destructive idempotent update with annotations and no output schema, the description supplies enough to call it correctly. It misses only permission/ownership caveats and sibling routing, which are not strictly required here.

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 all three parameters (id, userId, role) are already documented in the schema including the enum. The description adds no format or syntactic detail beyond 'specific user in a specific album', 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?

States a specific verb (update), resource (album user), and field (role), plus the exact endpoint PUT /albums/{id}/user/{userId}. An agent can distinguish it from immich_update_user_admin (global user) and immich_add_users_to_album, though the description never names those siblings explicitly to make the distinction airtight.

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 scopes usage to 'a specific user in a specific album', which implies when to reach for it, but there is no explicit when-to-use/when-not guidance or named alternative (e.g. add vs. update vs. remove album user). Basic context is there, exclusions are not.

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