28 tools with consistent naming (verb_noun pattern) and basic descriptions. All tools have input schemas with typed parameters and descriptions. However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and omit guidance on side effects. No output schemas documented. Error handling absent. Missing idempotency guidance for write operations. Parameter descriptions are terse and lack constraints (e.g., no enum for parse_mode values, no range for limit/offset). No mention of required permissions or audit trails. Tools like ban_chat_member and delete_message are destructive but lack confirmation patterns or dry-run support.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use send_message for text; use send_photo for images with captions'), prerequisites (e.g., 'Requires admin permissions'), and side effects (e.g., 'Irreversible, cannot be undone').
• Document output schemas for all tools. Specify returned fields (message_id, chat_id, user_id, etc.) so agents can chain calls. Example: send_message returns {message_id: int, chat_id: string, date: ISO8601}.
• Add enums for constrained parameters: parse_mode = ['Markdown', 'MarkdownV2', 'HTML']; type (in send_poll) = ['regular', 'quiz']. Replace free-form descriptions with formal JSON Schema constraints.
• Implement confirmation patterns for destructive tools. Add a dry_run parameter or require explicit confirmation via a separate confirm_delete_message(message_id) tool. Return clear error messages: 'Cannot delete message older than 48 hours' instead of raw API errors.
• Add error handling guidance to tool descriptions. Example: 'If chat_id is invalid, returns error with available channels. If user lacks permissions, returns 403 with required scope (e.g., manage_chat).'