keycloak_get_role_composites

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds behavioral value by warning that roleId must be the UUID, not the name, and by pointing to the source tool for that UUID. It does not mention recursion or pagination, but for a simple read-only list this is acceptable.

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, no filler. The primary action is stated first; the important identification caveat is front-loaded next. Every sentence 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?

For a simple read-only operation, the description covers the core usage and the key input pitfall. No output schema exists, but the action implies the return is the list of contained roles. It could optionally clarify whether nested composites are expanded, but that is not required for correct basic invocation.

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 coverage is 100% and already describes roleId as 'Role UUID, from the `id` field of a role.' The description adds the explicit negative constraint 'not its name' and the cross-reference for obtaining the correct value, which is meaningful disambiguation 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?

States a specific action ('List the roles contained in a composite role') on a clear resource. The immediate caveat about using UUID rather than name further distinguishes it from role-lookup siblings like keycloak_get_realm_role.

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 provides clear context: use this when you have a composite role and want its contained roles. It also supplies a cross-reference to keycloak_get_realm_role to obtain the needed UUID, which is a practical prerequisite. It does not explicitly list when not to use it or compare with alternatives, but the intended use is evident.

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