Server has 4 tools with basic schemas and descriptions, but significant gaps prevent production use. All tools have descriptions (10-70 chars, mostly short), and input schemas are present with proper JSON Schema structure. However, parameter descriptions are sparse or missing entirely (e.g., 'manage_service' action param has no description), output schemas are undocumented, and error handling provides no recovery guidance. The 'manage_service' tool lacks descriptions for both the 'service' and 'action' parameters, violating the requirement that every parameter must have a description. No tool documents what it returns or how to chain results. Security concerns: no input validation visible, no rate limiting, and destructive operations (stop/restart) lack confirmation patterns.

• Add descriptions to all parameters. For 'manage_service', document: service='Service name (e.g., sshd, nginx.service)', action='Operation to perform: start (begin service), stop (halt service), restart (stop then start), reload (reload config without stopping).'
• Document output schemas for each tool. E.g., get_service_state returns {status: string, substate: string}; list_failed_services returns {failed_units: [{name: string, load_state: string}]}.
• Add input validation: sanitize service names against [a-zA-Z0-9._-]+ pattern before passing to execSync(). Return 'Invalid service name' error with the constraint.
• Implement confirmation pattern for manage_service: add a 'confirm' parameter (boolean, default false). When false, return a summary of what would happen; when true, execute. This prevents accidental service stops.
• Enhance error messages with recovery hints. E.g., 'Service sshd not found. Available services: ssh, sshd.service. Try list_failed_services() to see failed units.'

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

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