Create Group

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

Annotations indicate it is a write operation (readOnlyHint=false) and not idempotent. The description adds only that it 'creates', but does not disclose potential failure modes (e.g., duplicate name/path), rate limits, or that it is a POST request. Minimal behavioral context beyond 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 short sentence, but it is under-specified. It lacks structure (e.g., bullet points for parameters) and omits essential information, making it less useful than a more verbose but complete description.

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 5 parameters, no output schema, and annotations with openWorldHint=true (ambiguous), the description is woefully incomplete. It does not explain return values, error states, or how to use the tool effectively (e.g., when parent_id is needed).

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 and 5 parameters (2 required), the description provides no parameter details. It does not explain parent_id for subgroups, visibility options, or description formatting. This is a critical gap.

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 ('Create') and the resource ('GitLab group or subgroup'). It distinguishes from other create tools like create_issue or create_merge_request. However, it does not explain the difference between a group and a subgroup (i.e., the role of parent_id).

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 (e.g., create_project, create_group_wiki_page). No prerequisites or context (e.g., authentication, namespace existence) are mentioned.

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