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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the 'Owners only' authorization requirement and the fact that pending invitations are included in the result. This is good added value, though it omits pagination or result-size behavior.

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 enumerating scope and membership fields, closed by the 'Owners only' constraint. Every clause earns its place and nothing is padded.

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 read-only list tool with no output schema and full parameter documentation, the description usefully enumerates the returned fields and the authorization requirement. It is nearly complete, missing only minor operational details like ordering or whether paused members are still counted.

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% and the single 'workspace' parameter is fully documented in the schema itself, including the hint that it is only needed when you own multiple workspaces. The description adds nothing about the parameter, so the baseline 3 is correct when the schema carries the burden.

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 clear verb+resource (list workspace members) and enumerates the returned fields (name, email, workspace role, paused status, agent access role) plus pending invitations, which fairly well distinguishes it from siblings like list_workspaces. However, it never explicitly contrasts itself with adjacent tools such as list_workspaces or invite_member, so it falls short of the 5 bar for stated sibling differentiation.

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 only usage-oriented guidance is the trailing 'Owners only', which is a permission precondition rather than a when-to-use rule. There is no explicit statement of when to choose this over list_workspaces or when it is inappropriate (e.g., for workspaces you don't own). Usage is implied rather than directed.

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