clickup_delete_chat_message

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

Annotations already mark the tool as destructive and idempotent. The description adds context about permanence, inclusion of replies, confirmation response, and error behavior (returning an 'Error ...' string). This goes beyond the annotations and provides valuable behavioral insights.

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 well-structured with clear sections, no redundant sentences, and front-loaded with the core purpose. Every section earns its place without unnecessary verbosity.

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 description covers the main aspects: purpose, usage guidance, error handling, and return type. It mentions deleting replies, which is not obvious. However, it does not discuss the optional workspace_id parameter or permissions, but the schema fills some gaps. Given the tool's simplicity and the presence of an output schema, it is mostly complete.

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?

Despite the schema providing descriptions for both parameters (message_id and workspace_id), the tool description only mentions message_id in the example and does not explain workspace_id. Since schema description coverage is 0% (meaning the description does not cover parameters), it fails to compensate for the missing parameter info. The example helps but is insufficient for complete understanding.

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 verb 'delete' and the resource 'Chat message' with the scope 'and its replies'. It distinguishes itself from the sibling tool 'clickup_update_chat_message' by explicitly stating when not to use it and suggesting the alternative.

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 provides explicit 'When to Use' and 'When NOT to Use' sections, including the exact alternative tool. It also covers error handling with a specific HTTP status code and return format, giving complete guidance.

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