list-members

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

The readOnlyHint annotation already establishes that this tool does not mutate state. The description adds a small amount of context with the endpoint and OAuth scope, but it discloses no further behavioral traits such as what members are included, how results are ordered, or whether the response is paginated. There is no contradiction with the annotations.

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 extremely concise and front-loaded: it states the action first, then provides the endpoint and scope in a compact format. Every element is informative and there is no redundant or filler wording.

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 simple list operation with readOnly annotation and fully documented parameters, the description is largely complete. It includes the endpoint and required scope, which helps the agent understand context. The main gap is the absence of any information about the return shape, but that is partially mitigated by the simplicity of a list operation and the lack of an output 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?

All three parameters (q, page, itemsPerPage) are already fully described in the input schema, so the description does not need to re-explain them. It also adds no additional semantic detail at the parameter level, so a baseline 3 is appropriate due to the high schema coverage.

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 action and resource: 'List team members', and reinforces it with the HTTP endpoint and required scope. It is unambiguous, though it does not explicitly differentiate itself from sibling tools like get-member or list-people beyond the plural 'members' in the tool name and description.

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 provides no direct guidance on when to use this tool versus alternatives such as get-member, invite-member, or change-member-role. The 'members:read' scope is useful context, but it does not explain selection criteria or when a different member-related tool would be more appropriate.

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