Two tools with complete schemas and detailed descriptions. build_and_install has a comprehensive 6-parameter schema with proper types, enums, and descriptions (pattern:constrained-input). list_devices is minimal but correct. Descriptions are well-written (180+ chars for build_and_install), explaining WHAT, WHEN, and routing logic. However, no tool annotations (readOnlyHint/destructiveHint), no error recovery guidance in descriptions, and no output schema documentation. Parameters lack explicit validation constraints (e.g., min/max for osVersion). Missing idempotency guidance for the write operation.

• Add tool annotations: mark build_and_install with destructiveHint=true (modifies device state), list_devices with readOnlyHint=true. Use MCP SDK's tool annotation API.
• Document output schemas in tool definitions. For build_and_install, declare: {build: {artifactPath: string, platform: string, profile: string}, install: {target: {kind: string, id: string, name: string, platform: string}, message: string}}. For list_devices, declare: {devices: [{id: string, name: string, platform: string, type: 'physical'|'simulator'|'emulator'}]}.
• Add error recovery guidance to build_and_install description: 'If osVersion is required for cloud devices, include it in the device name (e.g., "iPhone 15 Pro Max 17") or pass osVersion explicitly. If the device is not found locally, ensure it is connected or use a valid BrowserStack device name.'
• Constrain osVersion parameter: update description to 'BrowserStack OS version (integer or decimal, e.g., "17" or "17.0"). iOS: 10-18, Android: 8-15. Required for cloud devices.'
• Document list_devices output structure in description: 'Returns a list of connected iOS/Android devices, simulators, and emulators with their names, IDs, platforms, and types. Use device names from this list as the device parameter in build_and_install.'