Delete channel

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

The description discloses the critical two-call confirmation gate: the first call deletes nothing and returns a preview plus confirm_token, and deletion only occurs on the second call. It also explains that deleting a category leaves its channels in place, uncategorized. This adds valuable nuance beyond the annotations' destructiveHint=true and is not contradictory.

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 concise sentences, front-loaded with the primary purpose. Each sentence provides necessary context—purpose, usage flow, and category behavior—without redundancy or filler.

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 destructive nature and lack of output schema, the description fully covers the essential workflow: first call returns preview and token, second call completes deletion. It also covers the category edge case. The rationale for the confirmation gate is provided, making the tool's behavior complete for an agent to invoke 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?

The description adds meaning to the confirm_token parameter by explaining its role in the two-step deletion flow, and it clarifies that the channel parameter accepts both channel and category names. However, other parameters (guild, reason, dry_run) are not explained in the description and lack schema descriptions, leaving a gap in coverage.

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 first sentence 'Delete a channel or category' uses a specific verb and resource, making the tool's purpose unmistakable. It also distinguishes from sibling tools like create_channel, update_channel, and clone_channel by explicitly limiting scope to deletion of channels and categories.

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 gives explicit invocation guidance: 'When the user asks to delete something, call this and relay the preview for their go-ahead.' It also compares the tool to manual Discord usage, directing the agent to use this tool instead. The two-step flow with confirm_token is clearly explained, leaving no ambiguity about when and how to use it.

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