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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real value beyond that: it discloses the returned shape (members with roles, plus open invitations) and that all mutation paths live in the dashboard, so an agent knows this tool can never change membership.

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, zero filler. The read scope is front-loaded and the dashboard-mutation boundary follows immediately; every clause earns its place.

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 one-parameter, no-output-schema read tool this covers what an agent needs: what is returned, which scope it applies to, and that writes are impossible here. A brief note on ordering, pagination, or behavior for a large workspace is the only thing missing, and it is minor.

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 documented as name, slug or id with a default of the only workspace, so the schema carries the semantics. The description only implies scoping ('one workspace') without adding format or default behavior beyond what the schema states, which is the baseline-3 case.

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 names a specific resource ('the people in one workspace with their roles') plus the secondary payload ('invitations still open there'), which lets an agent distinguish it from list_workspaces and from the analytics siblings. It omits an explicit verb like 'list', but the noun phrase and title make the operation unambiguous.

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 second sentence usefully excludes mutations ('Members, roles and invitations are changed in the dashboard'), telling the agent not to look for write capability here. However, it never names an alternative tool or states the condition for calling it, e.g. how it relates to list_workspaces or when to prefer this over fetching a workspace object.

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