telbot MCP server exposes 9 tools for Telkomsel account management. Tools have descriptive names and are well-documented at the natural language level. However, critical gaps exist: (1) Input schemas are visible in code but parameter descriptions are often generic or missing type constraints (e.g., 'interval_minutes' lacks min/max bounds for a high-risk auto-purchase feature); (2) Output schemas are completely undocumented, no structured response format is declared, forcing LLMs to infer what fields get_profile, get_quota, buy_package return; (3) Error handling provides recovery guidance in some cases but lacks systematic categorization (retryable vs. user-fixable vs. fatal); (4) High-risk operations (buy_package, start_auto_buy) lack confirmation-step or dry-run patterns; (5) All tools accept only positional/literal inputs, no enum constraints for payment_method despite it being restricted to 'pulsa' or 'qris'. Naming is strong (verb-first, action-clear). Descriptions are moderate length (100-200 chars, within baseline). Per-tool analysis below.

• Declare output schemas for all tools. For get_profile, document: returns {name: string, balance: number, account_status: string, ...}. For get_recommended_offers, return {offers: [{offer_id: string, price: number, validity: string, ...}], total_count: number}.
• Add enum constraint to payment_method in buy_package: enum: ['pulsa', 'qris'] in JSON Schema. Update description: 'Payment method (enum: pulsa, qris).'
• Add min/max bounds to interval_minutes in start_auto_buy: minimum: 1, maximum: 1440 (1 day). Update description: 'How often to check quota, in minutes. Valid range: 1 - 1440.'
• Make threshold_mb required or set a default in schema. If default is 0, declare it: 'Default: 0 MB (buy only when completely empty).' Update schema property: required: true or default: 0.
• Implement confirmation-step pattern for buy_package and start_auto_buy. Add a dry_run parameter (boolean, default false). If true, return estimated cost without charging. Or introduce a separate preview_package tool, then require explicit confirmation via a confirm_purchase tool.
• Enhance error messages with recovery guidance. E.g., 'Failed to get quota: network timeout. Retry in 5 seconds. If problem persists, try logout and login again.' Categorize errors: retryable (network, timeout), user-fixable (invalid session, expired token), fatal (API removed).
• Update login description: 'Phone must be a local Indonesian number without country code (e.g., 812xxxxxxxx, exactly 10-11 digits). Will trigger OTP via SMS.'
• Update submit_otp description: 'Must be called immediately after login. Session expires after 10 minutes without OTP submission.'