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 of behavioral disclosure. It states it 'returns a dictionary containing workspace information,' which hints at read-only behavior but doesn't explicitly confirm safety (e.g., no side effects). It omits critical details like authentication requirements, rate limits, error conditions, or what specific information is included (e.g., team name, ID, settings). For a tool with zero annotation coverage, this is insufficient.

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 brief and front-loaded, with the core purpose in the first sentence and return value in the second. There's no wasted text, and it's structured for quick comprehension. However, the second sentence could be integrated more smoothly (e.g., 'Returns a dictionary with workspace information'), slightly affecting flow.

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 has no parameters, an output schema exists (which should document the return structure), and no annotations, the description is minimally adequate. It states the purpose and return type, but lacks behavioral context (e.g., safety, auth) and doesn't leverage the output schema to clarify what 'workspace information' entails. For a simple read operation, it's passable but leaves gaps.

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 schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain parameters, so it appropriately avoids redundancy. A baseline of 4 is applied as it efficiently handles the parameter-less case without unnecessary elaboration.

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 ('Get') and resource ('information about the Slack workspace/team'), making the purpose immediately understandable. It distinguishes from siblings like get_user_info or get_channel_info by specifying workspace-level information. However, it doesn't explicitly contrast with other workspace-related tools (none exist in the sibling list), so it falls short of a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication needs), typical use cases, or how it differs from other info-fetching tools like get_bot_info or get_user_info. This leaves the agent without context for tool selection.

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