Remove user from album

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing behavioral beyond repeating the DELETE endpoint; it does not say what the removed user loses (e.g., whether their contributed assets remain in the album) or what permissions are required.

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?

Short and front-loaded, with the core action stated first and the raw operation last. The only waste is the leading line that restates the title verbatim before the actual sentence, a minor redundancy.

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 simple two-parameter mutation with rich annotations and a 100%-covered schema, the definition is adequate: purpose, endpoints, and the "me" special case are all present. It is still thin on the consequences of removal (what happens to the user's assets in the album) and on permission requirements, which an agent managing an album would want.

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 both id ("Album ID") and userId ("Album user ID, or 'me'...") are already fully documented. The description's only parameter note — the "me" alias — duplicates the schema, so this is the baseline 3.

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 precise verb+resource ("Remove a user from an album") and includes the underlying operation (DELETE /albums/{id}/user/{userId}), which distinguishes it cleanly from siblings like immich_add_users_to_album and immich_update_album_user (role change). An agent can select it without opening the schema.

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?

It offers one concrete usage tip — using an ID of "me" to leave a shared album — which is genuinely helpful, but it never explains when to choose this tool over related ones such as immich_update_album_user (change a member's role) or immich_remove_partner. Usage is implied rather than routed.

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