Slack MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists workspaces and indicates the active one, which is useful behavioral context. However, it lacks details on permissions needed, rate limits, error conditions, or the format of the returned list (e.g., pagination, fields included), leaving gaps for a tool with no annotation coverage.

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 two concise sentences that are front-loaded with the core purpose ('List all connected Slack workspaces') and add valuable context ('Shows available workspaces and indicates which one is currently active'). Every sentence earns its place with no wasted words.

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?

Given the tool's low complexity (0 parameters, no annotations, no output schema), the description is reasonably complete for a simple listing operation. However, without annotations or an output schema, it could benefit from more detail on the return format (e.g., structure of the list, what 'active' means) to fully guide the agent, leaving room for improvement.

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 has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, so it appropriately focuses on the tool's purpose. A baseline of 4 is applied as there are no parameters to document.

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 clearly states the verb 'List' and the resource 'all connected Slack workspaces', specifying it shows available workspaces and indicates the active one. This distinguishes it from sibling tools like 'slack_get_current_workspace' (which might return only the active workspace) and 'slack_list_channels/users/files' (which list other resources).

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 description implies usage context by stating it lists workspaces and shows which is active, suggesting it's for discovering or managing workspace connections. However, it does not explicitly state when to use this tool versus alternatives like 'slack_get_current_workspace' or 'slack_switch_workspace', nor does it provide exclusions or prerequisites.

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