List admin events

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description restates read-only and idempotent, but adds context about the type of events (admin operations) and the response format (JSON array). No contradictions.

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?

Two sentences, front-loaded with 'Read-only', no superfluous words. Every sentence adds value: first states purpose and read-only nature, second gives usage guidance and alternative.

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 low parameter count, comprehensive annotations, and clear purpose differentiation from siblings, the description is complete. It explains what the tool does, its safety profile, when to use it, and the output format.

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% for the single max parameter. The description adds the default value (20) and clarifies it's an integer range, which goes beyond the schema's min/max constraints. However, it doesn't explain the effect of different values.

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?

Clearly states it returns admin events as JSON array, specific verb 'list' implied, and distinguishes from keycloak_events_login. The description includes example event types (CREATE, UPDATE, DELETE) which adds precision.

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?

Explicitly states when to use: for auditing admin changes. Directly contrasts with keycloak_events_login for end-user activity. Provides clear alternative, fulfilling the 'when not to use' guidance.

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