get_realm_role_client_composites

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

Description only says 'Get' with no behavioral details. No annotations provided to compensate. It does not mention that it is a read-only operation, whether authentication is required, or any side effects. Minimal disclosure beyond the obvious verb.

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?

Single sentence with no redundancy. Front-loaded with the key action and resource. Every word 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?

No output schema, so description should explain what 'client-level composites' are or what the response structure looks like. It lacks completeness for a tool with three parameters and no further context, especially given the complexity of Keycloak role mappings.

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?

Schemas provide 100% coverage with clear descriptions. The tool description adds no extra meaning, but per guidelines, baseline 3 is appropriate when schema already documents all parameters sufficiently.

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 exactly what the tool does: retrieve client-level composites of a realm role for a specific client. This clearly distinguishes it from siblings like get_realm_role_composites (which may return all composites) and get_client_role_composites (for client roles).

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?

No guidance on when to use this vs. alternatives. For example, it does not explain the difference between 'client-level composites' and 'realm-level composites,' leaving the agent to infer from context. Missing explicit conditions or exclusions.

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