remove_users_from_group

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

Annotations provide 'destructiveHint: true', but the description does not add any behavioral context beyond that. It does not mention effects like error handling for non-existent users, irreversibility, or permission requirements. Annotation contradiction: false.

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, front-loaded, no fluff. It is concise but perhaps overly brief for a tool with multiple parameters and destructive behavior. Earns a 4 for efficiency, not penalized for brevity since it still communicates core purpose.

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?

Tool has 4 parameters, destructive effect, and no output schema. Description lacks context on return behavior, permission requirements, partial success/failure scenarios, and contrast with sibling tools. Incomplete for an agent to use correctly.

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 description coverage is 100%, so the schema already defines parameters. The description adds no extra meaning or guidance on how to use the multiple user-identifier options (e.g., whether they are combined with OR/AND). Baseline 3 is appropriate given high schema coverage but no added value.

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?

Description is a clear verb+resource statement: 'Remove users from a user group'. It matches the tool name and directly states the action and target. It distinguishes from sibling 'add_users_to_group'.

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 versus alternatives. It does not explain selection among parameters (userIds, usernames, emailAddresses) or prerequisites (e.g., user must be in group). Sibling 'add_users_to_group' is present but no differentiation.

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