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

With no annotations, the description carries the full burden, and it does add real value by disclosing that visibility varies by caller role (admins also see invitations and their status) and that tokens are never returned. It omits permission requirements, pagination behavior, and ordering, so it is partial rather than complete.

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?

Two tight sentences with zero filler, front-loading the core action and then the role-dependent visibility caveat. Every clause carries information.

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 one-parameter list tool with no annotations and no output schema, the description covers what is returned (people with roles) and the key role-based variation (invitations for admins) and the token redaction guarantee. Missing pagination and result-size expectations keeps it from a 5.

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% for the single workspaceId parameter, so the description is the only source of meaning. 'In this workspace' loosely implies a workspace identifier but adds no format, constraint, or scope detail beyond the schema's uuid pattern.

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?

States a specific verb+resource (list the people in this workspace) plus the role vocabulary returned, which is concrete and non-tautological. It does not explicitly distinguish itself from sibling members_preview or members_accept, so it stops short of a 5.

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 implied by the resource name and the workspace-scoped framing, but there is no explicit when-to-use, no mention of the members_preview/members_invite alternatives, and no stated prerequisites. An agent can infer intent but gets no routing guidance.

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