Remove group member

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

Annotations already indicate destructiveHint=true, so the description adds the requirement for confirmation. However, the description contradicts the schema by implying the confirm parameter is mandatory when it is not required. This ambiguity lowers the score.

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 brief (one sentence) but under-specified given three parameters and no output schema. It could be improved by front-loading key usage instructions.

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?

Given no output schema and minimal parameter coverage, the description lacks completeness. It does not describe prerequisites, side effects, return values, or error conditions, and the confirmation requirement is ambiguous.

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 does not explain the meaning of groupId, userId, or the confirm parameter. The confirmation requirement mentioned is not mapped to the parameter, leaving the agent unclear about how to proceed.

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 action 'Remove a user from a group,' which aligns with the tool name and distinguishes it from sibling tools like keycloak_group_member_add and keycloak_group_delete.

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 no guidance on when to use this tool versus alternatives, such as when to use keycloak_group_delete instead. It does not clarify that the confirm parameter should be set to true, nor does it specify any prerequisites.

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