redmine_add_group_user

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

The description mentions it honors REDMINE_MCP_READ_ONLY, which provides a behavioral constraint. However, with no annotations provided, the description should disclose more, such as permissions required, side effects, or error conditions. The read-only note is helpful but insufficient.

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 concise at two sentences, with no unnecessary words. The purpose is front-loaded, and the behavioral note follows efficiently.

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?

With a simple tool and an output schema, the description need not explain return values, but it lacks essential context such as how to obtain valid user_id and group_id, and whether adding a duplicate user causes an error. The zero schema coverage and missing usage guidance make it incomplete.

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 0%, so the description must explain the parameters. It does not define user_id or group_id, leaving the agent without context on what values to provide or where to find them.

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 'Add a user to a group,' which is a specific verb and resource. This distinguishes it from sibling tools like redmine_remove_group_user and redmine_create_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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., whether the group and user must exist) 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.