Log out user

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

Annotations already signal destructiveHint=true and idempotentHint=false. The description adds 'Requires confirmation', indicating a safeguard. However, it does not elaborate on what happens if confirm is false or other behavioral details, such as irreversibility beyond what annotations imply.

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 concise but overly terse. It front-loads the purpose but omits critical details like parameter roles and return value. It could be restructured to include a brief usage note without adding much length.

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?

Given the destructive nature and lack of output schema, the description should provide more context about the confirm parameter behavior, success/failure indicators, and potential side effects. The current description leaves significant gaps for an agent relying on it alone.

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?

With 0% schema description coverage, the description should clarify parameters. It mentions 'user's sessions' (implying id) and 'Requires confirmation' (hinting at confirm), but does not explicitly state that confirm must be true to execute, nor does it describe the id format. This is insufficient for a two-parameter tool.

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 clearly identifies the action: revoking all sessions of a user. It uses a specific verb-resource pair and distinguishes from siblings like keycloak_user_sessions_list (which lists sessions) by indicating this tool revokes 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?

No guidance is provided on when to use this tool versus alternatives, such as keycloak_user_reset_password or keycloak_user_set_enabled. There is no mention of prerequisites or conditions (e.g., user must be logged in), leaving the agent to infer usage from context.

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