clickup_comment_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool as 'destructive and irreversible,' specifies that 'the comment and any threaded replies are removed,' and mentions the return value ('Returns an empty object on success'). This covers critical behavioral traits like permanence, scope of deletion, and output format.

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 front-loaded with the core purpose, followed by behavioral warnings and usage alternatives, all in three efficient sentences. Every sentence adds value without redundancy, making it highly concise and well-structured.

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 tool's complexity (destructive operation with no annotations and no output schema), the description provides complete context: it explains the action, warns about irreversibility, offers an alternative, and specifies the return value. This adequately compensates for the lack of structured fields, ensuring the agent understands how to use it 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 schema description coverage is 100%, so the input schema already documents the comment_id parameter thoroughly. The description does not add any additional parameter information beyond what's in the schema, such as format details or examples. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 specific action ('permanently delete'), the resource ('a ClickUp comment'), and the scope ('from a task, list, or view'). It distinguishes itself from sibling tools like clickup_comment_update by emphasizing destructive deletion versus marking as resolved.

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?

It explicitly provides when to use this tool ('permanently delete') versus an alternative ('Use clickup_comment_update with resolved=true instead if you only want to mark the comment as handled'). This gives clear guidance on choosing between destructive and non-destructive actions.

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