keycloak_get_realm_role_members

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

Annotations declare readOnlyHint=true, and the description is consistent with that. However, the description adds no behavioral detail beyond purpose—no mention of pagination behavior, return format, or whether membership is direct vs. effective. It does not contradict the annotations.

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 efficient sentence with a clarifying parenthetical. It is front-loaded and contains no filler.

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 read-only list tool, the purpose and pagination params are documented, and annotations cover safety. However, the description does not specify the output format or whether membership is direct vs. inherited, and it lacks usage differentiation from siblings. This is acceptable but leaves some gaps.

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 75%; roleName lacks a description, but the tool description clarifies that it identifies the role whose members are listed. The other parameters (max, first, realm) are already described in the schema. The description adds minimal parameter-level meaning 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 uses a specific verb ('List') and resource ('users who have a given realm role'), plus the clarifying question 'who has this role?' This clearly conveys the tool's purpose and differentiates it from sibling tools like get_group_members or get_user_role_mappings.

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?

Usage is implied through the 'who has this role?' phrasing, but there is no explicit guidance on when to choose this tool over alternatives such as keycloak_get_group_members or keycloak_get_user_role_mappings. No exclusions or alternative tool names are mentioned.

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