remove_user_group

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds no behavioral context beyond the verb 'removes.' It does not disclose potential effects on users assigned to the group, failure modes, or reversibility, missing an opportunity to add value beyond the 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?

The description is a single concise sentence with no filler or redundancy. It is front-loaded and easy to parse, though it is sparse enough that the conciseness comes at the cost of missing operational details.

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 having a simple schema and output schema, the description is insufficiently complete for a destructive operation. It omits guidance on the device parameter, prerequisites, error behavior, and consequences, making the agent reliant on external knowledge or trial-and-error.

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 must compensate for explaining parameters. It does not mention 'name' or 'device' at all, leaving the agent to guess the meaning of the optional device parameter and how name should be formatted or resolved.

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 states 'Removes a user group,' which is a specific verb+resource combination. It clearly distinguishes this tool from siblings like remove_user and remove_user_ssh_key by naming the exact resource being acted upon.

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, nor any prerequisites or conditions for removal. It does not mention checking for existing user groups, handling dependencies, or using get_user_group/list_user_groups first.

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