Strong foundation with 11 well-defined tools, comprehensive schemas using Zod validation, and clear descriptions. All tools have input schemas with proper type constraints (selectors bounded 1-2000 chars, timeouts 1-60000ms, filename regex validation). Descriptions are action-oriented and state destructiveness clearly. However, output schemas are not documented, responses are wrapped in generic Envelope objects without field-level documentation. Parameter descriptions are solid but could be more prescriptive about error recovery. Tool composition is clean (single responsibility per tool), and naming follows verb_noun convention consistently. Risk annotations (destructiveHint, idempotentHint) are present on mutation tools.

• Document output schemas for each tool. Add a 'Returns' section to each tool description specifying the structure of the 'data' field. E.g., launch_app returns {message: string, sessionId: string}; inspect_ui returns {elements: Array<{selector, text, visible}>}.
• Enhance error messages with recovery guidance. Replace 'Unable to launch the application' with 'Failed to launch app at {appPath}: {reason}. Verify the path exists and is executable, or try connect_app if the app is already running.'
• Add selector validation examples to click_element, type_text, wait_for_element, get_element_text, inspect_ui descriptions. E.g., 'CSS selector (e.g., #button-id, .class-name, [data-testid="submit"]). If selector matches 0 elements, tool returns error; if >100, only first 100 are processed.'
• Implement a dry-run or preview mode for launch_app and close_app. Add optional 'dryRun: boolean' parameter that validates inputs and returns what would happen without executing. Agents can then confirm before real execution.
• Document process lifecycle and recovery in connect_app and close_app descriptions. E.g., 'connect_app assumes the app process is already running on the specified port. If the process dies, subsequent calls will fail with connection error; use launch_app to restart. close_app only closes the WebDriver session, not the app process itself.'