redmine_remove_group_user

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

With no annotations, the description must disclose behavioral traits. It mentions honoring 'REDMINE_MCP_READ_ONLY', which hints at conditional behavior, but does not explain side effects, error conditions, or permission requirements. The tool is a mutation, yet no detail is given about the operation's impact.

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 two sentences and focuses on the core purpose. The first sentence is front-loaded with the essential action. The second sentence about the read-only flag adds some behavioral context but could be integrated. Overall, it is not verbose.

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 the lack of annotations and 0% schema coverage, the description is too brief. It fails to cover return values, error scenarios, authorization needs, or how this tool relates to siblings. The presence of an output schema is not utilized in the description.

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?

The input schema has 0% description coverage, so the description must compensate. It only implies the role of parameters via the purpose statement, but does not explain what 'group_id' and 'user_id' represent, how to obtain them, or any constraints.

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'), using a specific verb and resource. It distinguishes this tool from the sibling 'redmine_add_group_user' which performs the inverse operation.

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 is provided on when to use this tool versus alternatives like 'redmine_add_group_user'. There are no instructions on prerequisites, such as the user needing to be a member of the group, or when not to use it.

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