Permanently delete a Discord channel or thread by ID, with an optional audit log reason. This action cannot be undone.
Permanently delete a channel or thread. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Reason shown in the server audit log (optional) | |
| channel_id | Yes | Channel ID (a thread ID also works) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the description only needs to add specifics. 'Permanently' and 'This cannot be undone' add real weight by making clear that content is irrecoverable, which is stronger than the generic destructive flag, though it says nothing about permissions or what happens to the channel's messages.
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?
Two short sentences with the irreversible warning front-loaded. Nothing extraneous or repetitive.
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 two-parameter delete tool with full schema coverage and annotations carrying the safety profile, the description covers action, scope, and irreversibility. It could still note permission requirements or the fate of the channel's contents, but nothing essential for invocation is missing.
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%, with channel_id's ID pattern/thread note and the 'reason' audit-log purpose fully documented. The description adds no parameter detail, so baseline 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?
States a specific verb ('delete') and resource ('channel or thread') plus the permanence qualifier. The 'channel or thread' scope clearly separates it from discord_delete_message, discord_delete_role, and other delete siblings.
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?
No when-to-use guidance versus alternatives such as discord_edit_channel (to modify rather than remove) or discord_delete_message. No mention of required permissions (e.g., Manage Channels) or preconditions before calling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.