Single tool 'reply' has critical definition gaps. Description is in Russian and lacks English context for LLM selection. Input schema present but minimal (2 params, both strings). No output schema documented. No error handling guidance. Tool name 'reply' is generic and does not follow verb_noun pattern (should be 'send_message' or 'post_reply'). Parameter descriptions reference external context ('room_id брать из meta') rather than being self-contained. No indication of idempotency, retry safety, or side effects. Tool appears to be a write operation but lacks confirmation/dry-run pattern.

• Rename tool from 'reply' to 'send_room_message' or 'post_message' to follow verb_noun convention and clarify intent.
• Provide English description (50-200 chars): 'Send a text message to a Cognitive Core room. Requires room_id and message text in Russian. Returns message_id and timestamp on success.'
• Document output schema: {message_id: string, timestamp: ISO8601, room_id: string, status: 'sent'|'failed'}.
• Add error handling: specify which errors are retryable (network timeout, rate limit) vs. fatal (invalid room_id, auth failure), with recovery guidance.
• Rewrite parameter descriptions in English and make them self-contained: 'room_id: UUID of the target room (e.g., from incoming event metadata)' and 'text: Message body in Russian (max 4096 chars)'.