assign_mcp_user_groups

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states 'MUTATES access — confirm first' and 'Needs the MCP privilege,' conveying mutation side effects and permission requirements. It does not explain reversibility or effects on existing access, but the core behavior is transparent.

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 three concise sentences: purpose, parameter clarification, and safety warning. It is front-loaded with the primary action and contains no filler. Each sentence provides distinct value.

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?

For a simple two-parameter mutation without an output schema, the description covers purpose, mutation warning, and privilege requirement. It is missing an explicit description of 'handle' and any statement about return behavior, but given the tool's simplicity, it is nearly complete.

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 coverage is 0%, so the description must compensate. It explains that group_ids_json is a JSON array of group ids, which adds meaning beyond the raw schema. However, 'handle' is left unexplained, leaving one required parameter ambiguous. Partial compensation is provided, but not complete.

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 'Grant end-user groups access to an AI Hub MCP server,' clearly specifying the verb (grant), resource (end-user groups), and target (AI Hub MCP server). This distinguishes it from sibling tools like assign_mcp_tools, which assigns tools, and list_mcp_user_groups, which lists groups.

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 implies usage by stating the action ('Grant... access'), but it does not provide explicit guidance on when to use this over alternatives, nor does it mention exclusions. The 'MUTATES access — confirm first' warning provides a caution but not situational context. No alternative tools are referenced.

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