Server has 7 tools with mixed quality. Two tools share the same name (send_telegram_message), creating ambiguity. Descriptions are present but vary in quality, some are detailed (request_launch_approval: 280 chars), others minimal (get_bot_info: 31 chars, below 20-char threshold). All tools have input schemas with types, but parameter descriptions are sparse or missing. Output schemas are not documented. Error handling exists in code but is not reflected in tool descriptions. No tool annotations (readOnlyHint/destructiveHint) despite clear WRITE/READ_ONLY risk classifications in metadata.

• Rename one send_telegram_message to send_telegram_message_to_chat (or similar) to eliminate shadowing. Ensure both are registered with distinct names.
• Expand get_bot_info description to 50 - 150 chars explaining what bot metadata is returned and when to call it (e.g., 'Retrieve the bot's ID, username, and name for logging or verification').
• Document output schemas for all tools. E.g., get_chat_info returns {id: int, type: string, title?: string, ...}; broadcast_message returns {sent: int, failed: int}.
• Add tool annotations: mark send_notification, send_telegram_message, request_launch_approval, broadcast_message with destructiveHint=true; mark get_chat_info, get_bot_info with readOnlyHint=true.
• Add parameter descriptions to all tools. E.g., send_telegram_message parse_mode should state 'One of: HTML, Markdown, or None (plaintext). Defaults to HTML.'