Create a new text channel in a
Creates a new text channel in a Discord server with an optional topic and parent category
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | ||
| guildId | Yes | ||
| categoryId | No | Parent category ID to place the channel under | |
| channelName | Yes |
Changes observed during successful MCP inspections.
v1.5.0Input schema / properties / categoryIdAdded value: +{
+ "description": "Parent category ID to place the channel under",
+ "type": "string"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description covers the creation action and optional fields, but lacks details about required permissions, effects on existing channels, or behavior on failure. With no annotations, the description carries the full burden but falls short of full transparency.
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, concise sentence with no redundant content. It efficiently communicates the core action and optional parameters.
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?
With no output schema, the description need not explain return values, but it omits potential side effects, permission requirements, and error conditions. For a simple create operation, it is adequate but not fully complete.
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?
Only categoryId has a schema description. The description mentions 'topic' and 'parent category' but does not clarify guildId or channelName (though channelName is inferable). Schema coverage is 25%, so the description adds some value but leaves gaps.
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 a specific verb ('creates'), resource ('text channel in a Discord server'), and includes optional parameters ('topic and parent category'). It distinguishes itself from sibling tools like create_voice_channel and create_forum_channel.
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 guidance is given on when to use this tool versus alternatives such as create_voice_channel or create_category. The description only describes the action without contextual use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.