Delete a Discord channel or category. Requires channel ID and confirmation to prevent accidental removal.
Delete a channel or category (deleting a category does NOT delete its channels).
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| confirm | No | Set true to actually perform this destructive action | |
| channelId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that deleting a category does not delete channels, but omits important behavioral details like required permissions, need for confirm parameter to be true, and irreversibility.
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?
Single clear sentence that directly states the tool's purpose and a key caveat. No unnecessary 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?
No output schema, and the description lacks crucial context for a destructive action: no mention of permission requirements, the confirm parameter guard, or what happens on success/failure.
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 only 33% (only confirm has description). The description does not explain channelId or reason parameters, leaving them ambiguous beyond their names.
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 action 'Delete a channel or category' and specifies a key behavioral nuance (deleting category does NOT delete its channels), distinguishing it from other delete tools like discord_delete_message.
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 explicit when-to-use or when-not-to-use guidance. The description implies usage for deletion of channels/categories but does not mention prerequisites or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.