clickup_chat_reaction_add

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a mutation (adds reaction), requires authentication ('authenticated user'), has idempotent behavior ('no-op' for duplicate reactions), and returns an empty object on success. However, it doesn't mention potential errors, rate limits, or permission requirements.

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?

Two sentences with zero waste. First sentence states purpose and key behavior, second sentence describes return value. Every word earns its place, and information is front-loaded appropriately.

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?

For a mutation tool with no annotations and no output schema, the description provides good coverage: purpose, authentication context, idempotent behavior, and return value. It could be more complete by mentioning error cases or permission requirements, but it covers the essential context well given the tool's moderate complexity.

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 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Add an emoji reaction'), the resource ('to a ClickUp Chat message'), and the actor ('from the authenticated user'). It distinguishes from siblings like clickup_chat_reaction_remove (remove reaction) and clickup_chat_reaction_list (list reactions).

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 implies usage for adding reactions to chat messages but doesn't explicitly state when to use this vs. alternatives like clickup_chat_reaction_remove or other chat tools. It mentions the no-op behavior for duplicate reactions, which provides some context, but lacks explicit guidance on prerequisites or exclusions.

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