discord_delete_channel

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

With no annotations, the description carries the full burden; it does disclose the required MANAGE_CHANNELS permission, which is real behavioral value beyond the schema. However, for an unannotated destructive mutation it omits that deletion is permanent, what happens to existing messages, and whether the action is recoverable — significant gaps.

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?

A single sentence with zero filler, and the action is front-loaded ahead of the permission caveat.

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 one-parameter destructive tool with no annotations and no output schema, the definition covers what is deleted and the permission needed, but the omission of irreversibility and any post-delete effect leaves it only minimally adequate.

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 one parameter and schema description coverage is 100%, so the schema already documents channel_id fully. The description adds no format or sourcing detail (e.g. snowflake ID, obtainable via discord_list_guild_channels), leaving the baseline for schema-covered params.

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) scoped to a server, which cleanly separates it from siblings like discord_delete_role, discord_delete_invite, and discord_delete_message. It stops short of contrasting with discord_modify_channel (archive/rename), but the core purpose is unambiguous.

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 parenthetical gives the MANAGE_CHANNELS prerequisite, which is useful gating context, but there is no guidance on when to delete versus when to modify/archive a channel, and no note that deletion is irreversible. Usage is implied rather than instructed.

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