Server has 6 read-only tools with consistent naming (all verb_noun: get_*, search_*) and present descriptions (avg ~80 chars). All tools have input schemas with typed parameters and descriptions. However, descriptions are terse (under 100 chars) and lack context on WHEN to use each tool or dependencies between them. Output schemas are not documented. No error handling guidance. Sanitization module exists but is not integrated into tool responses. Missing tool annotations (readOnlyHint). Composition is reasonable, tools are single-responsibility, but parameter naming could be more explicit (e.g., 'chat_id' accepts multiple formats but description doesn't clarify precedence).

• Expand tool descriptions to 100-200 chars. Include WHEN to use: 'Retrieve recent conversations. Use this to discover available chats before calling get_messages. Supports pagination via offset_date.'
• Document output schemas for each tool. Example for get_dialogs: 'Returns {dialogs: [{id, title, unread_count, last_message_date}], total_count, has_more}'.
• Clarify parameter formats in descriptions. For chat_id: 'Chat identifier: username (e.g. @mychannel), integer ID (e.g. 123456789), or string ID (e.g. -1001234567890). Usernames are preferred.'
• Add error handling guidance. Example: 'If chat not found, returns error with available channels. If permission denied, returns error with required scope.'
• Declare tool annotations in schema. Add 'readOnlyHint: true' to all tool definitions so clients know these are safe to call without confirmation.