Remove a file from Slack by providing its file ID. Use this to clean up shared files and free workspace storage.
Delete a file from Slack.
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | File ID to delete |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It identifies the tool as destructive, but does not state whether deletion is permanent, what happens to shared links or references, or whether permission is required. This is a significant gap for a delete operation.
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, direct sentence with no filler or redundant information. It is appropriately front-loaded and easy to parse, fitting the tool's simplicity.
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?
The definition is minimally sufficient for a one-parameter delete tool, especially with full schema coverage. However, with no annotations and no usage guidance, it does not fully prepare an agent to understand the consequences or appropriate context of deleting a file.
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 schema covers the single parameter 'file' with 100% description coverage, defining it as 'File ID to delete'. The description adds no extra parameter meaning, so the baseline score 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 the specific verb 'Delete' with the resource 'file from Slack', making the action unambiguous. It is clearly distinct from sibling file tools like upload_file, list_files, get_file_info, and share_file.
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, nor any mention of prerequisites, permissions, or when deletion would be inappropriate. The agent is left to infer usage solely from the tool name and action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.