Single tool with minimal schema and generic description. The tool 'get_server_overview' has an empty input schema (no parameters), a 127-character description that lacks actionable context, and no documented output schema. No parameter descriptions exist (N/A due to empty schema). The description states WHAT the tool does but not WHEN to use it or what fields are returned. No error handling guidance. Tool naming follows verb_noun convention (positive), but overall definition quality is below baseline for production use.

• Document the output schema explicitly. Specify all returned fields (cpu_usage, memory_usage, load_average, network_stats, disk_usage, etc.) with types and descriptions so LLMs know what data is available.
• Expand the description to 150 - 250 characters. Add: WHEN to use (e.g., 'Call this to check server health before deploying'), WHAT it returns (e.g., 'Returns CPU, memory, disk, and network metrics'), and any prerequisites (e.g., 'Requires valid BT Panel credentials').
• Add error handling guidance. Document what errors can occur (connection timeout, auth failure, server offline) and suggest recovery steps (e.g., 'If connection fails, verify BT Panel URL and credentials via settings').
• Consider adding optional filter parameters (e.g., metrics: ['cpu', 'memory', 'disk']) to let agents request only needed data, reducing token overhead for large responses.
• Add related tools for common follow-ups: get_process_list, get_disk_usage_by_path, or trigger_alert_if_threshold_exceeded to enable multi-step server management workflows.