Retrieve sessions

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the raw REST mapping (GET /sessions) and says nothing about pagination, ordering, or the shape of a session object.

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 repeats the title verbatim, and the second sentence restates the same idea, so roughly half the text is redundant. The 'Immich operation' line is boilerplate metadata rather than task-relevant prose.

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 with full annotations, the core is covered, but with no output schema the description could reasonably describe what a session record contains and whether results are paginated. Those gaps leave the agent unable to anticipate the response.

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 the baseline is 4. There is nothing for the description to clarify beyond what the empty schema already communicates.

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 a list of sessions') and adds the scope qualifier 'for the user', which implicitly separates it from immich_get_user_sessions_admin. It does not explicitly name or contrast with any sibling, so an agent must infer the admin-vs-self distinction.

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 guidance. The phrase 'for the user' weakly implies this returns the authenticated user's own sessions rather than another user's, which is enough to imply usage but not to route confidently against immich_get_user_sessions_admin.

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