Delete a session

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the concrete DELETE /sessions/{id} operation and Sessions tag, but does not describe auth requirements, side effects, or whether the current session can be targeted.

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 description is short and front-loaded, with the operation line giving useful API context. The first line repeats the title 'Delete a session' exactly, which is slightly redundant, but overall it is efficiently structured.

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 one-parameter delete operation with full schema coverage and annotations covering destructiveness and idempotency, the description plus structured fields are largely complete. It does not explain potential effects on the caller's own session or authentication requirements, leaving minor context gaps.

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 fully documented in the schema with its uuid format. The description only says 'by id', adding no syntax or format meaning beyond the structured schema, so baseline 3 is appropriate.

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 ('Delete a session', 'Delete a specific session by id') and includes the underlying API operation. However, it does not explicitly distinguish this tool from close siblings such as immich_delete_all_sessions or immich_end_session, so it falls short of full sibling differentiation.

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 phrase 'by id' implies the tool is used when a specific session id is available, but there is no explicit guidance about when to choose this over immich_delete_all_sessions or immich_end_session. Usage is left to inference.

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