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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the behavioral detail that pending invites are included, which is useful context beyond the annotations. It doesn't mention pagination, ordering, or whether the response includes only active members vs all, but with annotations covering safety, a 3 is appropriate.

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?

One sentence, 12 words, front-loaded with the resource ('Everyone in the workspace') and immediately adds the distinguishing detail ('plus any invites still pending'). Zero waste, every word earns its place.

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 zero-parameter read-only list tool with an output schema present, the description is nearly complete. It tells the agent what the list contains (members, roles, pending invites). The only minor gap is not mentioning whether the list is paginated or ordered, but the output schema likely covers return structure. Given the tool's simplicity, this is adequate.

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?

The tool has zero parameters, so the schema is trivially complete (100% coverage). The description adds meaning by specifying what the returned list contains (members with roles and pending invites), which is the only semantic content needed. Baseline 4 for zero-param tools 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 the tool lists workspace members with their roles and pending invites. It uses a specific verb ('list') and resource ('workspace members'), and the mention of pending invites distinguishes it from a plain member list. However, it doesn't explicitly differentiate from sibling tools like get_workspace_info or list_identities, though the resource is clear enough.

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 implies usage: call this when you need to see who is in the workspace and their roles, including pending invites. It doesn't explicitly state when not to use it or name alternatives like list_identities or get_workspace_info, but the context of 'workspace members' vs 'identities' provides some implicit guidance. No explicit exclusions or alternative routing.

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