keycloak_get_group_members

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the semantic scope 'users in a group' but does not disclose behavioral details such as pagination behavior, the effect of briefRepresentation, or whether only direct members are returned. These are left to the input schema rather than the description.

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, short sentence that is front-loaded and precise. There is no filler or redundant wording; it contains exactly the necessary semantic content.

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 simple read-only listing tool, the description plus a fully described 5-parameter schema and readOnlyHint annotation cover most operational needs. The main gap is that it does not describe return shape or direct-members semantics, and there is no output schema to compensate, but overall the definition is sufficiently complete.

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%, and the schema already provides rich descriptions for all five parameters including groupId UUID semantics, max/first pagination, realm defaulting, and briefRepresentation guidance. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 'List the users in a group' uses a specific verb and resource, and directly conveys that this tool returns group members. It is clearly distinct from sibling tools like keycloak_get_user_groups, keycloak_get_group_role_mappings, and keycloak_list_users without needing to open any schemas.

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 implies the usage scenario: call this tool when you have a groupId and want the users in that group. However, it does not explicitly mention alternatives, exclusions, or when-not-to-use guidance relative to the many sibling list tools.

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