List login events

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description 'Read recent login events' is consistent with these annotations but adds no additional behavioral context (e.g., how recent, pagination, or rate limits). No contradiction.

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 concise sentence, which is appropriate for a simple tool. It covers the core purpose without unnecessary words, though it could include more detail without sacrificing conciseness.

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?

No output schema is provided, and the description does not explain what fields are returned or what 'recent' means. Given the low schema parameter coverage and lack of output details, the description is incomplete for a tool with 3 parameters and no explicit return structure.

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 input schema has 3 parameters (max, type, user) with 0% schema description coverage. The description only mentions 'optionally filtered' without explaining the meaning or role of any parameter, offering minimal added value beyond the schema.

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 'Read recent login events' which clearly identifies the verb ('Read') and resource ('login events'), and mentions optional filtering. However, it does not distinguish this tool from its sibling 'keycloak_events_admin' which lists admin events, missing a chance to clarify scope.

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 says 'optionally filtered' but provides no guidance on when to use this tool versus alternatives like keycloak_events_admin or keycloak_user_search. No explicit when-to-use or when-not-to-use information is given.

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