keycloak_get_realm_role

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

The annotations already declare readOnlyHint=true, so the read-only safety profile is covered. The description adds that the result includes attributes and composite flag, but it does not disclose not-found behavior, authorization requirements, or how the composite flag is represented. With annotations carrying the safety burden, a 3 is appropriate.

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?

One efficient sentence with no filler. The verb, resource, addressing key, and key output traits are all front-loaded, and every phrase earns its place.

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 complexity, complete parameter schema, and readOnlyHint annotation, the description is nearly sufficient. It identifies the resource, lookup method, and main returned fields, though it omits explicit not-found/error behavior and a full return shape since there is no output schema.

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%, so both realm and roleName are already documented. The description reinforces that roles are addressed by name, matching roleName's schema text, but it does not add format, defaulting, or interaction details beyond what the schema provides.

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 a specific verb ('Get'), a single resource ('one realm role'), and the lookup key ('by name'). It also previews the returned content ('attributes and composite flag'), which helps distinguish it from list_realm_roles and get_role_composites.

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: use this when you need a single realm role by name. However, it does not explicitly contrast with sibling tools like keycloak_list_realm_roles for enumeration or keycloak_get_role_composites for a separate composites endpoint, leaving some selection work to the agent.

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