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

Annotations already declare destructiveHint=true, and the description adds the detail that active sessions are disconnected and the action is irreversible. This complements the annotations well. However, it does not disclose any required permissions or impact on related entities (e.g., bots assigned to the channel).

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?

Two sentences, each essential and front-loaded. No redundant or vague phrasing. The warning about irreversibility is impactful and efficiently placed.

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 destructive operation with one parameter and no output schema, the description covers the key aspects: what is deleted, the irreversible nature, and the side effect on sessions. It could be improved by mentioning how to retrieve the channel ID or that the channel must exist, but overall it is sufficient.

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 coverage is 100% and the schema already describes the single parameter id as 'Unique identifier (UUID) of the channel to delete.' The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 the action ('permanently delete'), the resource ('WhatsApp channel'), and includes a specific side effect ('disconnect any active sessions'). This effectively distinguishes it from sibling delete tools like neuron_delete_social_channel or neuron_delete_bot.

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 use for permanent removal but does not explicitly state when to avoid it (e.g., if only temporary disconnection is needed) or reference alternatives like neuron_stop_channel_session. The 'cannot be undone' warning is helpful but insufficient guidance.

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