slack_disconnect

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

With no annotations, the description carries the full disclosure burden. It usefully reveals the downstream effect (sibling Slack tools stop reading) and that the change is reversible via Settings, which is real behavioral context. However, it does not state whether the Slack account/auth is untouched, whether in-flight operations are affected, or the scope of the toggle beyond Slack.

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?

A single front-loaded sentence with no filler. It is efficient, though the visible text is truncated ('Sett...'), which cuts off the final clause and leaves the sentence incomplete as presented.

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 simple zero-parameter toggle with no annotations and no output schema, the description covers the core effect and reversibility, which is roughly adequate. It stops short of clarifying the boundary between this local toggle and account-level disconnects, and the truncation leaves the re-enable instruction unfinished.

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 takes zero parameters, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies; nothing is missing on this dimension.

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 ('Turns Slack off in Local MCP'), which clearly separates it from siblings like slack_list_channels and slack_search_messages. It also clarifies this is a Local MCP toggle rather than an account-level disconnect. It does not, however, explicitly contrast itself against the many other *_disconnect tools.

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 when the tool is used (to stop Slack tools from reading the integration) but gives no explicit when-to-use/when-not guidance or named alternatives. The re-enable path is only hinted at ('until the user turns it back on in Local MCP's Settings').

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