FreeCAD MCP server has significant definition quality gaps. Tool names are action-oriented (ping_, run_, screenshot_, list_, get_, export_, validate_, open_) which is good. However, descriptions are inconsistent in quality and length. Most critically, parameter descriptions are sparse or missing entirely. For example, run_macro has only 2 parameters with descriptions, but no output schema documentation. The server exposes dangerous operations (run_macro executes arbitrary Python code) without confirmation patterns or clear risk documentation. No tool has documented return schemas, making it impossible for LLMs to plan downstream operations. Error handling is minimal, no recovery guidance, no categorization of retryable vs fatal errors.

• Document output schemas for all tools. For run_macro, specify: {success: boolean, stdout: string, stderr: string, result: any}. For screenshot_active_view, specify: {image_base64: string, width: integer, height: integer, format: string}. For list_objects, specify: {objects: [{name: string, type: string, geometry: object}], count: integer}.
• Add confirmation/dry-run pattern to run_macro. Implement a 'dry_run' boolean parameter (default false) that parses the code without executing it, or require explicit 'confirm_execution' parameter to prevent accidental destructive operations.
• Complete parameter descriptions. For run_macro_file: 'reset_documents (boolean, default true): Whether to close all open documents before running the macro. Set to false to preserve existing geometry.' For screenshot_active_view: 'view (string, enum: current|isometric|front|top|right|rear|bottom|left, default isometric): Camera orientation for the screenshot.'
• Add error recovery guidance. When ping_freecad fails, return: 'FreeCAD RPC server not responding on port 9875. Ensure FreeCAD is running and freecad_rpc_server.py has been loaded. Retry after 5 seconds or restart FreeCAD.' Use error classification: retryable (timeout, connection refused) vs fatal (port in use, permission denied).
• Enforce enum constraints in JSON Schema. For screenshot_active_view.view and open_in_slicer.slicer, add 'enum: [...]' to the schema definition, not just the description. This prevents LLM hallucination and enables client-side validation.