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

Annotations already declare this as a read-only, idempotent, closed-world operation, and the description adds genuinely new behavior: results are scoped to the current workspace unless one is passed, roles are constrained to owner/member, and pending invites appear only when the caller owns the workspace. It stops short of noting pagination or result ordering.

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 that carries the scope first and then the conditional invite detail, with no filler. The parenthetical aside is slightly awkward but costs little.

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 no output schema, the description must carry the return shape, and it only sketches it: members plus roles plus conditional invites, with no indication of structure, ordering, or how invitations are represented. Adequate for a simple read tool but leaves the response format under-specified.

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 coverage is 100% and the schema already explains the optional workspace name-or-id with its default. The description's '(or `workspace`)' only gestures at the parameter without adding format or fallback detail beyond the schema, so the baseline 3 applies.

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 sentence names the resource (workspace members) and specifies what is returned: each person's role (owner or member) and, conditionally, open invites. It implicitly distinguishes itself from list_workspaces and whoami by scoping to a single workspace's membership, though it never states the verb 'list' explicitly.

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 choose this over sibling tools such as list_workspaces, whoami, or find_people_for_role. The only routing hint, 'See list_workspaces', lives in the schema rather than the description, so an agent gets no explicit usage conditions here.

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