list_group_members

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds a useful behavioral trait—optional name/username search—but does not disclose other behaviors like pagination, sorting, or whether inherited members are included by default (though include_inheritance is in the schema). It neither contradicts annotations nor enhances the safety signal.

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 sentence of 13 words, front-loaded with the primary action ('List members of a GitLab group') followed by the key optional modifier. Every word earns its place; there is no redundancy or verbose detail.

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 list operation with strong annotations (readOnlyHint, openWorldHint) and a fully described schema, the description provides the core purpose and the primary optional search feature. It does not mention pagination parameters, but these are clearly documented in the schema. Since there is no output schema, the description could mention return format, but the domain (GitLab members) makes this fairly predictable. Overall, it is sufficient for the tool's complexity.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description's mention of 'optional name or username search' maps directly to the query parameter, which the schema already describes as 'Search for members by name or username.' Thus, the description adds minimal extra meaning beyond the schema, but it is consistent.

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 uses the specific verb 'List' with the resource 'members of a GitLab group,' clearly identifying the tool's function. It distinguishes from sibling tools like list_project_members by specifying the scope as group members, and further adds the optional search capability, making its purpose unmistakable.

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 clear context that this tool is for listing GitLab group members, and the optional search hint suggests use cases involving filtering by name or username. However, it does not explicitly contrast with alternative sibling tools such as list_project_members or get_users, so it lacks explicit exclusions or alternative guidance.

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