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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is covered. The description adds that pending invitations are included in the result set, which is useful beyond the annotations, but it is otherwise redundant by restating 'Read-only' and gives no pagination, auth, or result-detail context.

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 short sentences, front-loaded with the core action and result scope. There is no filler, and the 'Read-only' note is brief even if redundant.

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 simple read-only list tool, the description names the two returned categories (members and pending invitations) and safety is handled by annotations. However, it omits pagination behavior, does not clarify the ambiguous workspaceId/workspace_id parameters, and gives no guidance on the nested query override, leaving notable gaps.

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 description mentions no parameters at all. With only 50% schema description coverage and a required workspaceId plus an optional duplicate workspace_id, brand_id, and nested query object, the description does not compensate for the schema gaps or clarify which workspace identifier to use.

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 ('List') and resource ('workspace's active members and pending invitations'), with scope clearly bounded to members and invitations. An agent can distinguish this from sibling workspace tools like list_workspaces or invite_workspace_member without opening the schema.

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 purpose implies when to use it — to enumerate workspace members and pending invites — but it gives no explicit when-to-use guidance, exclusions, or alternatives. It does not say how it differs from list_workspaces or what to use for other workspace-member operations.

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