clickup_delete_comment

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

Annotations already indicate destructive and non-read-only. The description adds that deletion is permanent, works uniformly on all comment types, returns a confirmation string or error, and handles 404 specifically. No contradictions with 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?

Every section serves a purpose: API call, usage guidelines, return type, example, error handling. No fluff, well-organized.

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?

Covered: purpose, HTTP method, when to use/not use, return format, example, error handling. Output schema exists but description still explains return values. No gaps for a simple deletion tool.

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 0%, so the description should compensate, but it only includes an example without adding meaning beyond the schema's description of comment_id. The parameter is simple, but the description does not provide additional guidance on obtaining the ID or edge cases.

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 starts with a clear verb-resource pair: 'Permanently delete a comment.' It also specifies the HTTP endpoint and distinguishes from sibling clickup_update_comment.

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?

Provides explicit when-to-use ('to remove a comment posted in error or no longer relevant') and when-not-to-use ('to just fix wording or mark it resolved — use clickup_update_comment instead'). Clearly contrasts with a sibling tool.

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