discord_delete_channel

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add meaningful context by warning about the confirmation gate ('Requires confirm=true when confirmation is enabled'), which is a legitimate behavioral constraint. However, it omits critical traits of a destructive operation: the deletion is implied to be permanent, and there is no mention of permissions, cascading effects on messages, or what happens when confirmation is enabled but confirm=false.

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 two sentences are economical and every word earns its place; the main action is front-loaded ('Delete a channel') and the precondition follows immediately. It loses a point only because it is so terse that it sacrifices behavioral and parameter context.

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?

This is a destructive 4-parameter mutation tool with zero annotations and 0% schema description coverage, yet the description fills almost none of that gap. It fails to explain the required channel_id semantics, the role of guild_id, whether deletion cascades to messages, or the behavior when confirmation is enabled but confirm is not true. Even with an output schema present, an agent cannot confidently invoke this tool correctly.

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 0%, and the description barely compensates. It offers a semantic hint about the confirm parameter (true required under confirmation), but leaves channel_id (the required parameter), reason, and guild_id entirely unexplained. An agent cannot confidently determine what guild_id does, whether reason is for an audit log, or what values are expected for the other parameters.

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 uses a specific verb 'Delete' and resource 'channel', clearly stating the tool's function. It effectively distinguishes from sibling tools like discord_delete_role, discord_delete_message, and discord_delete_invite by naming the channel as the target resource, though it does not explicitly contrast itself with 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 guidance is given on when to use this tool versus alternatives such as discord_edit_channel or discord_move_channel. The only conditional guidance ('Requires confirm=true when confirmation is enabled') addresses a parameter requirement rather than tool selection. There are no when-not-to-use or exclusions noted.

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