Remove a realm role from a user

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

Annotations already indicate destructiveHint=true and idempotentHint=false. The description adds 'Requires confirmation', which aligns with the destructive nature, but doesn't elaborate on other behaviors like immediate effect or cascading effects.

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 very short (two sentences) and front-loaded with the core purpose. However, it might be too concise given the lack of parameter details. No wasted words, but could be improved.

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?

Despite only 3 parameters and no output schema, the description is too minimal. It doesn't explain the effect of revocation, the confirm parameter's required value, or provide any usage context. Sibling tools help but the description alone is incomplete.

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?

With 0% schema description coverage, the description should explain the parameters. Only 'confirm' is hinted at by 'Requires confirmation', but userId and role are not described at all. The description adds little meaning 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?

The description clearly states the verb 'Revoke' and the resource 'a realm role from a user', which distinguishes it from sibling tools like keycloak_user_role_assign or keycloak_group_role_assign. The title and description match well.

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 tool vs alternatives (e.g., when to revoke vs assign roles, or differences from group role tools). The only additional note is 'Requires confirmation', but it doesn't explain context.

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