Retrieve user sessions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the concrete admin endpoint (GET /admin/users/{id}/sessions) and the admin tag, which confirms privilege requirements, but says nothing about what a session record contains or whether it is paginated.

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 duplicates the tool title verbatim before the actual sentence adds anything, and the operation/tag line is metadata rather than guidance. Front-loaded enough to be usable but carries one redundant sentence.

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 one-parameter read tool with full annotations this is close to sufficient, but with no output schema the description could say what a returned session includes. The endpoint line usefully confirms it is an admin-scoped read, which is the main thing an agent needs.

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 coverage is 100% and the single parameter is documented as a uuid in the schema. The description only implies the id is a user id via 'for a specific user', adding marginal meaning beyond the schema, 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 and resource ('Retrieve all sessions for a specific user') and the 'admin' name/tag plus 'for a specific user' scoping sets it apart from the personal immich_get_sessions. It stops just short of explicitly naming that sibling as the non-admin alternative.

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?

No when-to-use or when-not-to-use guidance. Nothing tells the agent that this is the admin path for inspecting another user's sessions versus immich_get_sessions (current user's sessions) or immich_search_users_admin (to find the id first). Usage is only weakly implied by the endpoint path.

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