Single tool 'open_mini_app' has a detailed description (250+ chars) and comprehensive parameter list with type unions and descriptions. However, the schema uses 'union' types without explicit JSON Schema format, making it non-standard. No output schema is documented. The tool description is verbose but lacks clarity on what the returned URL structure contains or how to use it. Parameter descriptions are present but some lack actionable constraints (e.g., 'bot' accepts 'username, id, or t.me link' but no validation rules). No error handling guidance provided. The tool performs a state-changing operation (tells bot server the app was launched) but this is buried in the description rather than prominently stated.

• Document the output schema explicitly: specify that the response is a JSON object with fields like 'url' (string), 'app_name' (string), 'expires_at' (ISO 8601 timestamp), etc. Include example response.
• Convert input schema from 'union' notation to standard JSON Schema using oneOf with explicit type definitions for each variant (e.g., bot_username, bot_id, bot_url).
• Add a 'destructiveHint: true' annotation to the tool definition to signal that calling this tool has side effects (notifies bot server). Include this in the description: 'Calling this tool notifies the bot's server that the account launched the app, it is not a read-only operation.'
• Provide validation rules for 'bot' parameter: 'Username: 5-32 alphanumeric chars (no spaces). ID: positive integer. URL: must start with t.me/ and contain valid username.'
• Add error handling section to description: 'If bot not found, returns error with available bots. If chat_id invalid, returns error with valid chat IDs. If app not accessible, returns error explaining why (e.g., bot disabled, app removed).'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry