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

With no annotations, the description carries the full burden and does well: it discloses conditional email visibility (same-org only), the privacy_warning present in results for non-owner-private workspaces, and an explicit boundary on what is not observable. It stops short of describing auth requirements or rate limits, but the disclosure of conditional output behavior is substantial.

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?

Front-loaded with purpose, then returns, then use case, then exclusions — a logical order with no filler sentences. The parenthetical asides are information-dense rather than wasteful, though the middle section is heavy enough to slow scanning slightly.

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?

There is no output schema, so the description must explain the return shape, and it does: enumerated fields for users and agents, the role enum, and the conditional privacy_warning. For a single-required-param read tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100% and the slug description already documents both accepted forms (bare and org-prefixed). The prose adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 and resource ('List principals with explicit access to a workspace') and immediately enumerates the exact entity types and role enum returned. It is clearly distinguishable from list_workspaces, get_workspace, and check_workspace_private without opening any 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?

Gives an explicit use case ('verify a workspace is actually shared before writing output the team is expected to see'), states a concrete limitation (does not show private-to-owner status, agent ownership, open invites, or file share links), and names the sibling to use instead: check_workspace_private. When-to-use, when-not-to-use, and the alternative are all covered.

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