clickup_delete_chat_channel

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

Annotations already set destructiveHint=true. Description adds that deletion is permanent and irreversible, and explains error responses (404, Error string). Could mention cascading effects, but overall adds meaningful context beyond annotations.

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?

Well-structured with clear sections: overview, when to use/not, returns, example, error handling. No redundant information; every sentence serves a 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?

Covers core aspects: purpose, usage boundaries, example, errors. Missing potential details like permission requirements, but given annotations and output schema, it is sufficiently complete for deletion.

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 0% but schema itself has descriptions for both parameters. The description only provides an example for channel_id and omits explanation of workspace_id. Minimal added value; does not compensate for the lack of schema descriptions.

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 tool permanently deletes a Chat channel (Channel, DM, or location-bound). It distinguishes from sibling tools like clickup_update_chat_channel by specifying that it is for deletion, not hiding/archiving.

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?

Explicitly provides 'When to Use' (remove an unneeded channel) and 'When NOT to Use' (hide/archive, recommending update instead). Includes an example and error handling, offering clear decision support.

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