EVE-NG MCP server has solid naming conventions (all tools start with action verbs: list_, get_, create_, delete_, add_, start_, stop_) and comprehensive parameter schemas with types and descriptions. However, descriptions are inconsistent in depth and quality. Most tool descriptions are adequate (100-200 chars) but lack actionable guidance on when to use them vs. similar tools. Parameter descriptions are present but often generic (e.g., 'Full lab path' without format examples). Output schemas are not explicitly documented, responses are formatted as JSON strings rather than structured objects with declared fields. Error handling is minimal: most tools catch EveNGClientError and return plain text error messages without recovery guidance or error classification. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Composition is good: tools are single-purpose and chainable (e.g., list_images → add_node). Security: credentials injected via environment variables (correct pattern). Overall: functional but lacks LLM-optimization patterns for error recovery, output structure, and tool selection clarity.

• Add tool annotations: mark list_labs, get_lab, list_images with readOnlyHint=true; mark delete_lab with destructiveHint=true; mark create_lab, add_node, start_node, stop_node, start_all, stop_all with appropriate hints.
• Document output schemas explicitly. Instead of returning JSON strings, define structured response objects with typed fields (e.g., Lab { name: string, path: string, nodes: Node[] }, Node { id: int, name: string, status: string }).
• Enhance error messages with recovery guidance: 'Lab not found at /path/to/lab.unl. Call list_labs() to see available labs.' Classify errors as retryable (network timeout) vs. user-fixable (invalid path) vs. fatal (permission denied).
• Add dry-run support to delete_lab: new parameter 'confirm: bool' (default false). When false, return what would be deleted without executing. Require confirm=true for actual deletion.
• Convert informal enum descriptions to JSON Schema enums. E.g., node_type should have enum: ['qemu', 'dynamips', 'iol', 'docker'] in schema, not just in description text.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry