diff --git a/extensions/commonly/src/tools.ts b/extensions/commonly/src/tools.ts index 12d8ced33f714..a54f2b61c85fb 100644 --- a/extensions/commonly/src/tools.ts +++ b/extensions/commonly/src/tools.ts @@ -410,7 +410,7 @@ export class CommonlyTools { name: "commonly_react_to_message", label: "Commonly React to Message", description: - "React to a chat message with an emoji AS the agent identity. Use for social-presence signal on a peer's contribution (👍 / 🎉 / 👀) or as a micro-ack for a one-liner that doesn't need a worded reply ('thanks' / 'got it' / 'agreed'). DON'T use as a substitute for a substantive reply when @-mentioned with a real request — post words then (or NO_REPLY when there's truly nothing to add). Reactions are bounded social presence, not bulk noise. Pass remove=true to remove a previously-added reaction of the same emoji. Same kernel endpoint humans use; observers see the badge appear live via socket.", + "React to a chat message with an emoji AS the agent identity. Pick the emoji that carries the MEANING, not a default: ✅ verified/confirmed-done, 🎉 shipped/milestone, 👀 I'll-look-at-this, 💡 good idea, 🔥 impressive work, ❤️ appreciation, 👍 plain agreement — 👍 is the weakest signal, so prefer a more specific one whenever it applies. Also usable as a micro-ack for a one-liner that doesn't need a worded reply ('thanks' / 'got it'). DON'T use as a substitute for a substantive reply when @-mentioned with a real request — post words then (or NO_REPLY when there's truly nothing to add). When an acknowledgement is all you'd post, react with `commonly_react_to_message` instead of posting or staying silent; never instead of a reply someone asked for. Reactions are bounded social presence, not bulk noise. Pass remove=true to remove a previously-added reaction of the same emoji. Same kernel endpoint humans use; observers see the badge appear live via socket.", parameters: Type.Object({ messageId: Type.String({ description: "Message ID to react to (from commonly_get_messages).",