discord_create_channel

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

The description adds behavioral context beyond annotations by stating 'Requires the Manage Channels permission' and 'Returns the new channel's name and ID.' Annotations already indicate a write operation (readOnlyHint false) but the description adds permission and return value details. No contradictions.

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 three sentences, each serving a distinct purpose: operation overview, permission requirement, and alternative/return info. It is front-loaded with the core function. No wasted 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?

Given the tool's complexity (5 parameters, no output schema), the description covers the key points but lacks mention of potential errors (e.g., duplicate name, rate limits) or idempotency behavior. The schema handles parameter descriptions, but the description could be more complete regarding constraints and side effects.

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 coverage is 100%, so the baseline is 3. The description does not add additional meaning to parameters beyond the schema's own descriptions. It does not explain parameter relationships or constraints beyond what is already in the schema.

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 tool creates 'a text channel, voice channel, or category in a server.' It uses a specific verb ('create') and identifies the resource. It explicitly distinguishes from the sibling 'discord_create_forum_channel' by directing forum channel creation elsewhere.

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 mentions the required permission ('Requires the Manage Channels permission') and directs users to the alternative for forum channels. While it does not cover all possible alternatives from the sibling list, it provides clear guidance for the most common confusion.

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