keycloak_get_user_sessions

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

The readOnlyHint annotation already covers the safety profile, and the description adds meaningful behavior beyond it: only active sessions are listed, and the returned information includes location and timing. This helps set expectations for a read-only listing operation.

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 a single front-loaded sentence with no filler or redundant detail. The verb and resource appear immediately, and the parenthetical adds useful scoping without bloating the text.

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 read-only list operation, the description plus detailed schema is sufficient: required parameter is documented, optional realm is clarified, and the return scope is summarized. The main gap is the absence of usage routing relative to sibling session tools, but this does not prevent correct invocation.

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%, and the schema already explains the realm default and clarifies that userId is a UUID, not a username, with a pointer to keycloak_list_users. The tool description itself adds no parameter-level meaning beyond this, 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 uses a specific verb ('List') and a precise resource ('a user's active SSO sessions'), with the parenthetical clarifying the kind of information returned. This clearly differentiates it from sibling tools like keycloak_get_client_sessions and keycloak_get_realm_session_stats.

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 description gives no explicit guidance on when to use this tool versus related session/realm tools, and it names no alternatives or exclusions. Usage context is only implied by the tool name and resource phrasing.

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