LocalPlay exposes 4 mouse control tools with basic verb-noun naming (move_mouse, mouse_click, mouse_drag, mouse_scroll). All tools have descriptions (50-80 chars) and input schemas with typed parameters. However, descriptions are minimal and lack context on WHEN to use each tool or what distinguishes them. Parameter descriptions are present but generic ('X coordinate' vs 'Target X coordinate for mouse movement'). No output schema documentation. Error handling returns plain strings without recovery guidance. Tools lack idempotency hints and destructive operation warnings despite performing system-level mouse control (WRITE risk). No pagination, no structured output, no tool annotations.

• Expand tool descriptions to 100-150 chars. Add WHEN guidance: 'Use move_mouse to position the cursor without clicking. Use mouse_click for single/multi-click operations. Use mouse_drag for drag-and-drop. Use mouse_scroll for wheel scrolling.'
• Document output schema as structured JSON: {success: bool, message: string, final_position: {x: int, y: int}, timestamp: ISO8601}. Return this from all tools instead of plain strings.
• Add error recovery hints: 'Invalid coordinates (outside screen bounds). Screen size is {width}x{height}. Retry with valid coordinates.' Include screen dimensions in error responses.
• Add tool annotations: mark all tools with destructiveHint=true (mouse control affects system state) and idempotentHint=false (repeated calls may have different effects if UI changed).
• Constrain numeric parameters: 'x: integer, 0 to {screen_width}' and 'y: integer, 0 to {screen_height}'. Query screen size at startup and document in tool descriptions.