Server has 4 tools with complete descriptions and basic input schemas. All tools are verb-noun named (analyze_, migrate_, recover_, extract_). Descriptions are substantive (100-200 chars), exceeding the 10-char minimum. However, parameter descriptions are minimal or absent, most params lack detail on format, constraints, or dependencies. Output schemas are not documented; tools return JSON strings without declared structure. Error handling is implicit (exceptions bubble up) rather than explicit recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles (analyze=READ_ONLY, migrate/recover/extract=WRITE). Missing pagination, rate limiting, and per-item error reporting for batch operations.

• Add formal enum constraint to 'target_device' parameter in migrate_project schema: {"enum": ["generic", "raspberrypi"]} instead of relying on description text.
• Document output schemas for all tools. E.g., analyze_project returns {"issues": [{"type": string, "severity": string, "location": string}], "total_issues": int}. Use JSON Schema in tool definition or a separate schema reference.
• Add tool annotations: @mcp.tool(..., readOnlyHint=True) for analyze_project; @mcp.tool(..., destructiveHint=True) for migrate_project, recover_project, extract_project.
• Wrap exceptions in try-except blocks and return structured error responses with recovery hints. E.g., catch FileNotFoundError and return {"error": "Project file not found", "suggestion": "Ensure path is absolute and file exists. Supported formats: .exp, .st, .xml, .pro"}.
• Add 'limit' parameter (default 50, max 500) to migrate_project and recover_project to cap output size. Document in description: 'Returns up to limit POUs and data types. Use pagination or split large projects.'