KubeWhisper has 7 tools with clear verb-noun naming (list_clusters, resolve_cluster, k8s_get_resources, prometheus_query, github_actions_runs, scale_deployment, send_slack_message). All tools have descriptions (10 - 200 chars, within baseline). Input schemas are present with type definitions and parameter descriptions. However, output schemas are NOT documented, responses are free-text strings rather than structured objects. Error handling is minimal; no recovery guidance or actionable error messages. The scale_deployment tool has a confirmation pattern (confirm=bool) which is good, but lacks explicit error classification. Missing: pagination for list tools, per-item success/failure reporting, and structured output formatting.

• Define output schemas for all tools. E.g., list_clusters should return {clusters: [{name, context, prometheus_url, keywords, namespaces}], default: string}. Document in tool docstrings or via MCP schema extensions.
• Add structured error responses with recovery guidance. E.g., 'Prometheus unavailable at {url}. Retry in 30s or check cluster configuration.' Include error_code, retryable (bool), and suggested_action fields.
• Implement pagination for list_clusters and github_actions_runs. Add limit (default 20, max 100) and offset/cursor parameters. Return total_count and next_cursor in response.
• Reduce k8s_get_resources output verbosity. Return only {resource_type, namespace, cluster, items: [{name, status, key_metrics}]} instead of raw Kubernetes fields. Omit internal metadata.
• Add explicit audit logging to scale_deployment. Log to stderr or a structured audit sink: {timestamp, caller, tool, cluster, deployment, replicas_before, replicas_after, confirm, result}.