Server defines 5 tools with basic schemas and descriptions, but exhibits critical gaps across naming, parameter documentation, and output specification. Tool names lack clear action verbs (e.g., 'message_complete_notification' is passive; 'start_intensive_chat' and 'stop_intensive_chat' are vague about what 'intensive' means). Descriptions are present but generic (avg ~60 chars, below 194-char baseline). Parameters lack type constraints and detailed format guidance. No output schemas documented. Error handling is absent, no recovery guidance, retryability classification, or actionable error messages. The tool set conflates UI interaction concerns (request_user_input, message_complete_notification) with session management (start/ask/stop_intensive_chat), violating single-responsibility principle.

• Rename 'message_complete_notification' to 'send_notification' (active verb). Rename 'start_intensive_chat' to 'create_chat_session' and 'stop_intensive_chat' to 'close_chat_session' (clearer intent).
• Document output schemas for all tools. E.g., 'start_intensive_chat' returns {sessionId: string, createdAt: ISO8601}. 'ask_intensive_chat' returns {response: string, timestamp: ISO8601}.
• Add format constraints to parameters: 'sessionId' (UUID format), 'predefinedOptions' (array of 1-10 strings, each 1-100 chars), 'timeout' (1-3600 seconds).
• Add error handling guidance: 'On timeout, returns {error: "timeout", retryable: true}. On invalid sessionId, returns {error: "session_not_found", retryable: false, suggestion: "Call start_intensive_chat first"}.'
• Expand descriptions to 100-200 chars with WHEN/WHY context. E.g., 'request_user_input: Prompt the user for input via a command-line window. Use this when the agent needs human confirmation or data entry. Supports predefined options for quick selection. Timeout after N seconds if no response.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry