Remove group member

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

Discloses destructive nature, confirmation requirement, non-idempotency, and return message behavior beyond what annotations already provide. No contradiction with annotations.

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?

Three sentences, front-loaded with purpose and nature, followed by guidance and return info. No redundant or missing information.

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?

Comprehensive for a simple tool with 3 fully described parameters and no output schema. Includes prerequisites, behavior with confirmation, and return value.

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%; descriptions are clear. The tool description adds minimal extra parameter-specific value, only contextualizing the confirmation gate and ID resolution flow.

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 tool removes a user from a group by IDs, distinguishing it from siblings like keycloak_group_member_add and keycloak_group_members_list.

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?

Explicitly provides prerequisites (resolve IDs with keycloak_group_list and keycloak_group_members_list first) and an alternative to reverse the operation (keycloak_group_member_add). Also notes it requires confirmation and is not idempotent.

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