Delete channel (IRREVERSIBLE)

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds significant value by explicitly stating 'THIS IS IRREVERSIBLE: all messages in the channel are lost and cannot be restored' and requiring confirm=true. This goes beyond the annotations and is directly relevant to the agent's decision-making.

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 two sentences, front-loaded with the core action 'Permanently delete'. It uses concise, high-impact warnings without fluff. Every sentence serves a purpose: stating the action and emphasizing irreversibility/acknowledgement.

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 tool is simple with two parameters and no output schema. The description covers the action, irreversibility, and confirm requirement. It does not mention what happens to child channels when deleting a category, but this is not essential for basic usage. The annotations plus description are sufficient for a destructive operation.

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 50% (only confirm is described). The description reinforces the confirm parameter's meaning and necessity. However, channel_id lacks a description in both schema and description, though its purpose is inferable from the tool name and pattern. The description does not fully compensate for the missing channel_id semantics.

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 clearly states 'Permanently delete a channel or category' – a specific verb and resource. It distinguishes itself from sibling tools like delete_role and reorder_channels by naming the exact action and target.

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 the tool ('when you need to permanently delete a channel/category') but does not explicitly mention alternatives or when not to use it. The warning about irreversibility and confirm flag provides some usage context, but not direct sibling differentiation.

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