End HLS streaming session

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 genuine behavioral context by stating it "releases server resources," but omits any auth requirements, error behavior, or what happens to an already-ended session.

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?

It is short, front-loaded, and every line contributes something. The only waste is the first line, which restates the title verbatim.

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 resource-release operation whose annotations already carry the safety profile and which has no output schema, the description is largely adequate. It falls short on parameter documentation and any usage context, leaving gaps an agent would have to infer.

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 only 50% (id and sessionId are documented as uuid, while key and slug have nothing). The endpoint template does show that id and sessionId are path parameters, adding some semantics, but the undocumented parameters are left unexplained in both schema and description.

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 gives a specific verb and resource ("End HLS streaming session") and reinforces it with the underlying DELETE endpoint, making the scope unambiguous. It is clearly distinct from auth-related session siblings (immich_delete_session, immich_lock_session) because it names HLS streaming, though it never explicitly contrasts itself with them.

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 guidance on when to call this versus alternatives, nor any prerequisites (e.g. that a stream must first be started via immich_play_asset_video). The description only states purpose, leaving usage entirely to inference.

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