Get GitLab project member

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

Annotations already cover the read-only, idempotent, and non-destructive nature, so the description adds value by clarifying that inherited memberships are included and that the effective access level is computed. This is behavioral context not present in the structured fields and enriches the agent's understanding.

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, front-loaded sentence that immediately conveys the action, scope, and output. Every word contributes meaning, and there is no redundant or filler content.

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?

This is a simple read-only GET with only two parameters, clear annotations, and an output schema. The description covers the essential behavioral aspects (single member, direct/inherited, effective level) and does not need to explain return values since the output schema is already provided. It is fully adequate for selecting and invoking the 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 project parameter is well-documented in the schema, but user_id only has type constraints. The description implies user_id identifies the member whose membership is being fetched, but it does not explicitly define its meaning or format. With schema coverage at 50%, the description only partially compensates for the missing user_id details.

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 a specific verb ('Get') and clearly identifies the resource ('one direct or inherited project member') and the key returned value ('effective access level'). It distinguishes itself from siblings like list_project_members by focusing on a single member, and from get_group_member by specifying project membership.

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 phrase 'Get one' implies this is for a single member lookup, but there is no explicit guidance on when to choose this over list_project_members or get_group_member. The description does not state exclusions or alternatives, leaving usage largely implied through the word 'one' and 'project member'.

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