List team members

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond a basic listing statement—no mention of pagination behavior (despite a cursor parameter), ordering, or what fields are returned. For a list operation with existing annotations, this is thin but does not contradict 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 a single short sentence—appropriately concise for such a simple tool. However, it leaves out critical usage details that this brevity could have accommodated, making the conciseness feel more like under-specification than earned efficiency.

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?

With 3 parameters (including pagination cursor/limit), no output schema, and 33% schema coverage, the description is notably incomplete. It doesn't explain pagination semantics, response structure, or membership roles. The project_id param is well documented in the schema, but the cursor/limit pagination mechanism is completely unexplained. For a paginated tool this is a meaningful gap.

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 only 33%; only project_id has a description. The description itself names no parameters. The cursor and limit parameters for pagination receive zero explanation in either the schema or description—the agent must infer how to paginate through results. This in an area where the description should have compensated.

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 tool name and title are clear ('list team members'), and the description states the purpose simply. However, it doesn't distinguish from sibling tools like list_team_invites or update_team_member_role, and it doesn't clarify scope (e.g., all members vs. active members). It's minimally adequate but not differentiating among the many team-related siblings.

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?

There is no guidance on when to use this tool versus alternatives like list_team_invites, update_team_member_role, or remove_team_member. No mention of what a 'team member' includes or excludes relative to pending invites. The description provides zero context for selection among the several team-related sibling tools.

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