clickup_delete_chat_reaction

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

Annotations already indicate destructive and idempotent behavior. The description adds error handling details (404 response) and mentions the reaction is sent as a path segment, but does not discuss rate limits or other side effects. Adds moderate value 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?

The description is well-structured with clear sections (overview, when to use, when not to use, returns, examples, error handling). Each sentence is purposeful and concise, with no fluff.

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 that an output schema exists, the description appropriately includes a brief 'Returns' statement. It covers error scenarios (e.g., 404) and usage guidelines. For a simple delete operation, this is complete and contextual.

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 input schema already describes all parameters with clear descriptions. The description provides an example and error handling but does not add new semantic meaning beyond what schema states. Baseline is 3 due to high schema coverage.

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 'Remove an emoji reaction from a Chat message.' It uses a specific verb and resource, and distinguishes from the sibling tool 'clickup_add_chat_reaction' by explicitly contrasting the use case.

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 sections 'When to Use' and 'When NOT to Use', guiding the agent to only undo reactions and not add them, with a clear alternative tool reference.

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