list_project_members

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

The description explicitly states that it is read-only and does not mutate data, reinforcing the readOnlyHint. It also discloses that missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors, adding value beyond annotations. The description doesn't cover pagination behavior details beyond what schema provides, but the error disclosure is valuable.

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 concise with three sentences, front-loaded with the primary purpose, then usage guidance, then behavioral notes. The third sentence about parameter usage is somewhat redundant with the schema, but not excessive. Overall well-structured and efficient.

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 read-only list tool with a comprehensive schema (100% coverage) and clear error-handling disclosure, the description is adequately complete. It covers collection vs single resource, read-only safety, error conditions, and parameter usage. Pagination isn't detailed, but schema covers it, and no output schema exists. The description could mention the lack of project-level inheritance details, but that's parameter-specific and already in schema.

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 100%, so the schema documents all 7 parameters. The description reinforces the need to use numeric ID or URL-encoded path for project_id and to use required identifiers and pagination fields, but it doesn't add new semantics beyond what schema descriptions already provide. Thus baseline 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 'List members of a GitLab project' with a specific verb and resource. It distinguishes itself from sibling tools like 'get_project' and 'list_group_members' by explicitly mentioning project vs group context and collection vs single resource.

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 advises using the get tool for a single resource versus the list tool for a collection, providing clear usage context. It doesn't explicitly mention when not to use this tool or alternatives like list_group_members, but the collection vs single distinction is sufficient guidance.

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