Delete channel

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

The description fully explains the non-destructive first call and the confirm_token mechanism, adding behavioral context beyond the annotations (readOnlyHint=false, destructiveHint=true). No contradiction.

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?

Four sentences front-loaded with purpose. It is reasonably concise, though some minor redundancy could be trimmed. Overall effective.

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?

The description covers the deletion behavior, safety mechanism, and category effect. It lacks details on the preview return format, but given no output schema, it provides sufficient context for an agent to use the 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?

The description adds meaning to dry_run and confirm_token by explaining their role in the two-step process. However, it does not elaborate on channel, guild, or reason beyond their schema descriptions, leaving some gaps for a low-coverage (40%) 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 states 'Delete a channel or category' with a specific verb and resource, and distinguishes it from sibling tools like delete_message or delete_role by explicitly targeting 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 provides clear guidance: it explains the two-step dry-run/confirm pattern, instructs the agent to call this directly and relay the preview, and notes that deleting a category leaves channels uncategorized.

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