Logout

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds concrete behavioral context beyond that by stating the session token is invalidated, which tells the agent the operational consequence.

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?

Very short and front-loaded: the effect statement follows the title immediately, and the operation/tag metadata is compact. Minor redundancy from repeating 'Logout' as both title and first word of the sentence, but nothing wasteful.

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, no-output-schema tool whose annotations already convey the safety profile, the description supplies everything needed to call it correctly: what it does and what happens to the session. Nothing critical is missing.

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 there is nothing for the description to document. Baseline of 4 applies, and no param semantics are missing.

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 ('logout') and resource ('current user') plus the resulting effect ('invalidate the session token'). It is clearly distinguishable from generic mutations, though it does not explicitly differentiate itself from close siblings like immich_logout_o_auth or immich_end_session.

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 use case (logging out the current user) is implied and self-evident, but the description offers no explicit when-to-use guidance or alternatives such as logout_o_auth or end_session. Adequate for a simple, unambiguous tool, but no routing help.

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