Server has 5 tools with basic naming (verb_noun pattern) and descriptions present. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool and dependencies between them. Output schemas are not documented. Error handling is absent, no guidance on recovery, retryable vs fatal errors, or actionable error messages. The send_message tool (WRITE operation) lacks confirmation/dry-run pattern. Parameter descriptions are terse and lack format/constraint details. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Call list_dialogs first to discover available chats, then get_chat_history to fetch messages from a specific chat'). State what the tool returns and any prerequisites.
• Document output schemas for all tools. Specify field names, types, and which fields are required for downstream tool calls (e.g., get_chat_history must return message_id, sender_id, timestamp for agent reasoning).
• Add tool annotations: mark get_me, list_dialogs, get_chat_history, search_messages with readOnlyHint=true; mark send_message with destructiveHint=true to signal that it modifies state.
• Enhance parameter descriptions with format/constraint details. E.g., 'chat: Chat identifier (numeric ID, @username, phone number, or "me"). Numeric IDs must be positive integers.' Add min/max for limit (e.g., 1-100).
• Implement error recovery guidance. Return actionable errors like 'Chat not found. Available chats: [list]. Call list_dialogs() to see all chats.' instead of bare exceptions.

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

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)