Retrieve all Slack workspace users in a single call. Use the limit parameter to control the number returned for efficient member listing.
List all users in the Slack workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of users to return |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states a basic listing action and does not mention pagination, the effect of the limit parameter, or the tension between 'all users' and the default limit of 200.
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?
The description is a single clear sentence with no filler. It is front-loaded with the action and resource, making it easy to scan.
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?
With no output schema and no annotations, the description should explain call behavior more fully. It omits limit-related behavior, pagination, and return expectations, leaving an important gap between 'list all users' and the actual limit parameter.
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 limit parameter already has a clear schema description. The tool description adds no extra parameter meaning, so the baseline of 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?
The description uses a specific verb ('List') and resource ('all users in the Slack workspace'), making the tool's purpose clear. It is implicitly distinguishable from single-user siblings like get_user_info, but it does not explicitly name an alternative or scope boundary.
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 guidance on when to use this tool versus alternatives such as get_user_info or get_user_by_email. The intended usage must be inferred from the tool name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.