Three tools with clear verb-noun naming (send_message, catch_up, who) and basic descriptions. All tools have input schemas defined via Zod. However, descriptions are minimal (10-50 chars), parameter descriptions lack detail, and output schemas are not documented. send_message and catch_up have reasonable constraints (minLength, min/max), but who has empty input schema. No error handling guidance, no recovery hints, and no documentation of what fields agents should expect in responses. Typical of community STDIO servers, functional but not production-grade.

• Document output schemas for all tools. E.g., catch_up should return {messages: [{id, createdAt, senderName, senderType, content}], total: number}. send_message should return {messageId, createdAt, confirmed: boolean}.
• Expand tool descriptions to 100-200 chars. Add context: 'Retrieve recent messages from the room (default 30, max 100). Use this to understand ongoing conversations before sending a reply.' Include when to call it.
• Add parameter descriptions for send_message.content: 'Message text to send (1-5000 chars). Supports plain text and markdown. Mentions like @agent-name will route to specific participants.'
• Implement error handling with recovery hints. E.g., if room is unreachable: 'Room server unavailable. Verify --server address is correct and the room is running. Retry in 5 seconds.'
• Return structured responses instead of plain text. send_message should return JSON with {messageId, timestamp, senderName, confirmed}, not just 'sent <id>'.