list_workspace_members

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful context about returned fields and the user_id lookup use case, but it does not disclose behavioral details like pagination defaults or response limits beyond what the schema already provides.

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 sentences, zero filler. The first sentence states the action and result fields; the second sentence gives a concrete workflow purpose. It is front-loaded and every clause contributes value.

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?

The description plus a 100%-covered schema and strong annotations is complete for a read-only list tool. It identifies the required workspace_id, optional filters, pagination parameters, output fields, and the follow-up operations it supports. No critical information needed to select or invoke the tool is missing.

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 100%, with workspace_id, role, email, page_size, and current_page all described in the input schema. The description does not add semantic meaning to the parameters themselves, so it earns the baseline score rather than extra credit.

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 uses a specific verb ('List'), a clear resource ('every member in a workspace'), and names the returned fields ('organization role, workspace role, status, and timestamps'). It also distinguishes itself from singular member operations like get_workspace_member by framing itself as the enumeration step.

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 explicitly says to use this tool to find a user_id before get_workspace_member, update_workspace_member, or remove_workspace_member, giving concrete invocation context. It does not, however, contrast itself with other list tools such as list_all_users or state when not to use it, so it stops short of full exclusion guidance.

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