Server provides 6 tools with documented schemas and descriptions. Tool naming follows verb_noun convention (create_session, list_sessions, get_session, delete_session, pause_session, send_message). Descriptions are present but many lack depth about when to use tools or prerequisites. Parameter descriptions exist but could be more detailed about constraints and dependencies. No error handling guidance visible in tool definitions. Output schemas are not documented in the provided code. Missing context about idempotency, destructiveness, and multi-step workflows.

• Document output schemas for all 6 tools. Specify what fields create_session returns (session_id, created_at, etc.), what list_sessions returns (array of session objects with total count), what send_message returns (response text, token counts, timestamp). Use JSON Schema format in code or inline documentation.
• Add destructiveness/idempotence annotations to tool descriptions. Mark delete_session as 'DESTRUCTIVE, this permanently deletes the session and all conversation history. No recovery possible.' Mark send_message as 'IDEMPOTENT, sending the same message twice to the same session produces the same response.'
• Expand parameter descriptions with constraints and enums. For permission_mode, document: 'Permission mode for Claude Code execution (enum: plan, auto-edit, bypassPermissions). Default: plan. See Claude documentation for semantics.'
• Add error handling guidance to descriptions. For get_session: 'Returns session details and recent messages. If session_id not found, returns 404 with 'session not found' message. Try list_sessions to find valid IDs.'
• Clarify when to use each tool. Update list_sessions description: 'List all sessions with optional filters. Use this to discover session IDs before calling get_session or send_message.' Update get_session: 'Retrieve full details and conversation history of a single session. Use after list_sessions to inspect a specific session.'
• Document numeric bounds for message_count in get_session: 'Number of recent messages to include (1 - 100, default 5). Higher values return more conversation context.'