delete_channel

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

The description states the destructive action, and annotations already mark it as destructive and not read-only. It does not add extra context like irreversibility, cascading deletions, or permission requirements beyond what the annotations imply.

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 words, directly conveying the tool's purpose.

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 simple one-parameter destructive action, the description provides enough context to understand the tool's core function. It does not mention returns or errors, but no output schema is present and the purpose is clear.

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?

The only parameter, channel_id, is not formally described in the schema, and the description only indirectly implies it identifies the channel or DM to act on. The parameter name is clear, but no additional constraints or clarifications are provided.

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?

Clearly states the action ('Delete'/'close') and the target resource ('a channel' or 'a DM'), making its purpose unambiguous and distinguishing it from sibling tools like 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?

The description implies when to use it (whenever a channel or DM needs to be removed) but does not explicitly mention alternatives, prerequisites, or scenarios where it should not be used.

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