Get current GitLab user

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds that it returns 'profile and identity' but doesn't disclose additional behavioral traits like whether it requires authentication or what happens if the token is invalid. With annotations covering the safety profile, a 3 is appropriate as the description adds some context but not rich behavioral detail.

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 that is concise and front-loaded with the action ('Return') and the resource ('profile and identity'). It contains zero waste and is appropriately sized for a simple tool with no parameters.

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 the tool's simplicity (no parameters, no nested objects, has output schema), the description is complete enough. The output schema likely describes the return structure, so the description doesn't need to explain return values. The description covers the purpose and the context of the connected token, which is sufficient for this tool.

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 tool has zero parameters, and the schema description coverage is 100% (vacuously true). Since there are no parameters to document, the description doesn't need to add parameter semantics. The baseline for 0 params is 4, and the description correctly implies no parameters are needed, so a 4 is appropriate.

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 tool returns the profile and identity associated with the connected GitLab token. It uses a specific verb ('Return') and resource ('profile and identity'), and it distinguishes itself from sibling tools like get_runtime_info or get_gitlab_capabilities by focusing on the user's identity. However, it doesn't explicitly differentiate from potential similar tools like get_project_member, but the context of 'current user' is clear.

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 when the agent needs the current user's profile or identity, but it doesn't provide explicit guidance on when to use this tool versus alternatives. It doesn't mention any exclusions or alternatives, but given the tool's simplicity and the fact that it's the only tool for getting the current user, the guidance is adequate but not explicit.

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