Critical gaps across all dimensions. Tool naming lacks consistency (duplicate 'send' and 'react' across platforms without platform prefix). Descriptions are minimal (10-30 chars) and lack actionable context. Input schemas present but sparse, no enums for constrained values, no min/max for numeric params, no output schemas documented. No error handling guidance. Security concerns: file paths accepted as parameters without validation. Composition issues: duplicate tool names across Discord/Telegram create ambiguity for LLM selection.

• Rename tools with platform prefix: 'discord_send', 'discord_fetch_messages', 'telegram_send', etc. This eliminates ambiguity and lets LLM select the correct platform without reading descriptions.
• Expand descriptions to 100-200 chars. Example: 'Send a message to a Discord channel or DM. Supports text, file attachments, and interactive buttons. Returns message_id for use in reply_to or react. Fails if channel_id is invalid or bot lacks permissions.'
• Document output schemas for all tools. Example: fetch_messages returns {messages: [{id, author, text, timestamp}], total_count, has_more}. This enables LLM to chain calls (e.g., extract message_id from fetch_messages, pass to react).
• Add parameter constraints: limit (1-100, default 50), emoji (non-empty string, max 2 chars or custom emoji ID), text (1-2000 chars for Discord, 1-4096 for Telegram). Include these in descriptions and JSON Schema.
• Implement strict path validation for files parameter. Whitelist only INBOX_DIR and reject any path containing '..', absolute paths, or symlinks. Return clear error: 'File must be in inbox directory: /home/user/.claude/channels/discord/inbox/'