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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying exactly which side effects are absent (no invitations, no role changes) and by scoping the result to 'the authorized workspace,' both relevant to the large sibling set.

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 with no filler. The action and scope are front-loaded, and the exclusion of invitation/role changes is stated immediately after, making the description easy to consume.

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 member list with optional pagination parameters and annotations that already establish safety, the description is nearly complete. It does not describe response shape or pagination behavior, but the tool name and schema make those inferable.

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 0%, so the description needed to compensate by explaining limit/offset semantics, but it says nothing about either parameter. The names and default/min/max values are partially self-explanatory, yet the description itself contributes no parameter-level meaning.

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 opens with a specific verb and resource: 'Inspect members of the authorized workspace.' It also distinguishes itself from mutation-focused siblings by explicitly saying it does not invite anyone or change roles, so an agent can separate it from send_workspace_invitation or update_member_expertise.

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?

It clearly presents the tool as read-only and states what it does not do ('Does not invite anyone or change roles'), giving useful negative guidance. It does not name the alternative tools to use for invitations or role changes, so the route to those siblings is left to inference.

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