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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered elsewhere. The description adds only that both members and their roles are returned. It says nothing about pagination behavior despite limit and cursor being present, nor about ordering or what happens when a project has no members.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity edges toward under-specification rather than crispness given the undocumented parameters.

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 three-parameter paginated list tool with no output schema and zero schema description coverage, the description is too thin. An agent knows what it returns conceptually but not how to page through results or what the member objects look like, which 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 0%, so the description carries the burden for all three parameters. It only indirectly conveys that project_id scopes the listing; limit and cursor are neither mentioned nor explained, leaving the pagination contract entirely undocumented anywhere an agent can see.

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?

Specific verb plus resource: 'Lists the people in a project and their roles.' This clearly separates it from the mutating siblings invite_project_member, put_project_member and revoke_project_member. It stops short of naming those siblings as alternatives, but the read-only collection listing intent is unambiguous.

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?

Usage is only implied by the verb 'Lists' - an agent can infer this is the read path for project membership versus invite/put/revoke. There is no explicit statement of when to choose this over get_project or list_projects, and no prerequisites or exclusions are given.

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