This is a DSH plugin, not a standard MCP server. It exposes 2 tools (movein_from_claude_code, movein_from_opencode) with basic parameter schemas but critical quality gaps. Tool descriptions are present but generic (under 200 chars). Parameter descriptions exist but lack detail on constraints, formats, and error recovery. No output schema documentation visible. No error handling guidance. The tools perform destructive file operations (WRITE risk) but lack confirmation/dry-run guidance in descriptions. Schema definitions are minimal, parameters have types but lack examples, constraints, or validation rules. No evidence of idempotency, pagination, or structured error responses.

• Document the output schema for both tools. Specify what fields are returned on success (e.g., { moved_items: [...], skipped: [...], errors: [...] }) and what structure each item contains.
• Enhance parameter descriptions with validation rules and examples. E.g., 'project: Absolute path to project root (must exist and be readable; e.g., /home/user/my-project). If omitted, uses DSH host process cwd.'
• Add explicit dry-run guidance to tool descriptions. E.g., 'By default (apply=false), this tool reports what would be moved without making changes. Set apply=true only after reviewing the dry-run report.'
• Define error categories and recovery steps. E.g., 'If path is invalid, verify it exists and is readable. If config is malformed, check syntax with [tool-name]. If permissions fail, ensure DSH has read access to the source directory.'
• Add output examples to descriptions showing typical success and error responses, so LLMs understand what to expect and how to interpret results.