Server provides 5 well-named, read-only monitoring tools with clear descriptions (avg 85 chars) and structured schemas. All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for planning. Error handling is minimal (generic try-catch blocks with no recovery guidance). Parameters lack constraints (e.g., limit has no min/max bounds). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Naming is strong (verb_noun pattern), but schema completeness and error guidance are weak.

• Document output schemas for all tools. For get_system_resources, specify: {cpu: {manufacturer, brand, cores, speed_ghz, current_load_percent}, memory: {total_gb, used_gb, free_gb, usage_percent}, disk: {filesystem, mount, total_gb, used_gb, usage_percent}, system: {platform, distro, hostname, uptime_hours}}. This enables LLMs to extract fields and plan downstream calls.
• Add min/max constraints to numeric parameters. E.g., limit: {type: 'number', minimum: 1, maximum: 1000, description: 'Number of items to return (1-1000, default: 20)'}. Prevents runaway queries.
• Enhance error messages with recovery guidance. Instead of 'Failed to list processes: {error}', return structured errors: {error: 'permission_denied', message: 'Cannot access process list. Ensure server runs with sufficient privileges.', retryable: false}. This guides LLM recovery.
• Add tool annotations to inputSchema. For all 5 tools, add 'readOnlyHint': true and 'idempotentHint': true to signal safety. Example: {type: 'object', properties: {...}, readOnlyHint: true, idempotentHint: true}.
• Clarify platform-specific behavior in descriptions. For get_system_logs, update description to: 'Get recent system logs from journalctl (Linux only). On non-Linux systems, returns an error. Requires journalctl to be available.' Add similar notes to get_docker_status for Docker availability.