Update user

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is partially covered. However, the description adds nothing about which user fields are mutable, whether password/admin/blocked changes have special consequences, or what authentication is needed for a 32-parameter mutation.

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 single sentence is short and front-loaded, but it essentially restates the title, so it does not fully earn its place. There is no structure to help an agent understand the parameter groups or operation scope.

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 mutation tool with 32 undocumented parameters, no output schema, and only partial annotation coverage, the description provides none of the context an agent needs to invoke it correctly. It is completely inadequate given 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?

Schema description coverage is 0% across 32 parameters, and the description mentions none of them. Critical fields such as user_id, email, password, admin, blocked, external, provider, and skips_confirmation are left completely undocumented by both schema and description.

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 adds only the word 'existing' beyond the title 'Update user' and the tool name gitlab_update_user. It never states which user attributes can be changed or how this differs from siblings like gitlab_create_user or gitlab_delete_user beyond the bare verb 'update'.

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 gitlab_create_user, gitlab_delete_user, or gitlab_get_user. No prerequisites, permission requirements, or exclusions are mentioned.

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