Three tools with basic verb-noun naming (list, read, send). All have descriptions and visible input schemas with types. However, descriptions are minimal (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not formally documented. No error handling guidance, no parameter validation hints, and no security/permission documentation. Tool composition is reasonable (single responsibility), but parameter design could be more user-friendly (e.g., accepting chat names instead of requiring IDs). Schemas present but sparse, missing min/max bounds, enums, and format constraints.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it, and what it returns. E.g., 'List all Bale chats registered via /register_chat command. Returns chat title, ID, type, and active status. Call this first to discover available chats before reading messages.'
• Add formal schema constraints: limit parameter should have minimum: 1, maximum: 300; text parameter should have maxLength: 4000; chat_title should be required and non-empty.
• Document output schemas in tool descriptions or as structured comments. E.g., 'Returns {ok: bool, count: int, chats: [{title, chat_id, chat_type, is_active}]}'.
• Add error handling guidance to descriptions. E.g., 'If chat_title is not found, call bale_list_chats to see registered chats. If send fails due to rate limit, retry after 5 seconds.'
• Add tool annotations: mark bale_send_message with destructiveHint: true and idempotentHint: false; mark bale_list_chats and bale_read_messages with readOnlyHint: true.