keycloak_list_required_actions

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

The annotations already declare readOnlyHint=true, so the description only needs to add behavioral context beyond that. It does clarify the returned information includes enabled/default flags, which is useful. However, it doesn't mention pagination, realm defaulting behavior, or other response characteristics, so the added transparency is modest.

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, focused sentence that front-loads the action and resource, then gives the key output detail. No filler or redundant phrasing.

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 list operation with one optional, well-documented parameter, the description is complete. It states what the tool lists and what information is returned, and the schema covers the only parameter. No output schema exists, so the description appropriately exposes the return semantics.

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?

The only parameter, realm, is fully described in the schema (100% coverage), including its default behavior. The description does not add new parameter semantics beyond what the schema already provides, so the baseline score 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 uses a specific verb ('List') and resource ('the realm's required actions'), and adds concrete detail about what is reported: whether each action is enabled or applied to new users by default. This clearly distinguishes it from the sibling list tools, none of which target required actions.

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 tool's purpose is immediately clear from the description: query the realm's required actions and their default/enabled state. It doesn't explicitly contrast with alternatives or state when not to use it, but for a simple read-only list tool this context is sufficient.

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