Get user

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description 'Fetches a single user by id' adds no extra behavioral context beyond the annotations—no rate limits, error behavior, or response format. It is essentially a restatement of the name.

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 clear sentence, front-loaded with the verb and no unnecessary words. It is appropriately minimal for a simple get-by-id operation.

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?

The description is very sparse: it does not mention return values, error handling, or any special behaviors. Since no output schema exists, the description carries more burden, but it fails to provide even basic context about what happens on success or failure.

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 100%, with user_id described as 'Numeric user id.' The tool description's 'by id' adds no new meaning beyond the parameter name and schema description, so the baseline of 3 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 'Fetches a single user by id,' specifying the verb and the resource. It distinguishes this tool from siblings like gitlab_list_users, which lists users.

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 the tool is for fetching a specific user by ID, but it does not explicitly state when to use it as opposed to alternatives or mention exclusions. No comparison to gitlab_list_users or other tools is provided.

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