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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one useful behavioral detail beyond that: results are scoped to the caller's current workspace and include each member's role. It says nothing about pagination or ordering, and no output schema exists to cover that.

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?

At six words it is maximally compact with nothing wasted, and the key qualifier 'current' is placed up front. The trade-off is that the terseness reads as a fragment rather than a sentence, leaving the action implicit.

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?

A zero-parameter read tool with full annotation coverage and no output schema has modest requirements, and the description at least indicates the returned fields (members plus role). It still leaves open whether pending invitations are excluded and whether all members or only a page are returned.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not introduce any confusing pseudo-parameters.

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 'Current workspace members with their role' identifies the resource (workspace members) and adds what is included (their role), but it is a noun fragment with no verb and closely echoes the tool name. It does partially distinguish from list_workspace_invitations by the word 'current', but does not make the distinction explicit.

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 when-to-use guidance and no mention of the two nearby siblings, list_workspace_invitations and list_workspace_roles, that an agent could easily confuse with this one. The agent must infer from the name alone that 'current' excludes pending invitations.

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