The server has 16 tools with generally complete input schemas and descriptions, but falls short in several key areas. All tools have schemas defined in JSON Schema format with proper types, and descriptions are present (though some are generic). However, parameter descriptions are inconsistent in quality, output schemas are not documented, error handling guidance is minimal, and there is no evidence of tool annotations (readOnlyHint, destructiveHint). The naming convention is solid (verb_noun pattern throughout), but composition could be tighter, several tools expose Kubernetes-specific details rather than abstracting complexity. Most tools are read-only (14 of 16), which is good for risk, but the three write tools (kubectl_scale_deployment, kubectl_restart_deployment, kubectl_edit_hpa) lack confirmation patterns or dry-run options. Tool chains are present (e.g., get then describe), but response structures are not documented, making it hard for LLMs to know what fields to expect downstream.

• Add output schema documentation for every tool. Example: 'kubectl_get returns a list of objects with fields: {name, namespace, status, age, ...}'. Include field types and which are IDs for chaining.
• Add tool annotations to every tool. For read tools, add readOnlyHint=true. For write tools (scale, restart, edit), add destructiveHint=true and idempotentHint=false (or true if idempotent).
• Expand write tool descriptions to warn of side effects and non-recoverability. E.g., 'WARNING: kubectl_restart_deployment triggers a rolling restart, causing pod downtime. This action is not easily undoable.'
• Implement dry-run support for write tools. Add a 'dry_run' boolean parameter (default false) to kubectl_scale_deployment, kubectl_restart_deployment, and kubectl_edit_hpa. Return what would change without making changes.
• Add error handling guidance to all tool descriptions. E.g., 'If pod not found, try calling kubectl_get with the same namespace to discover available pods.' or 'If permission denied, verify cluster credentials and RBAC roles.'
• Standardize namespace parameter documentation: 'Kubernetes namespace. If omitted, uses current context namespace. Pass '*' or leave empty for all namespaces.' Consistent behavior across all tools.
• Document practical limits for 'limit' and 'max' parameters. E.g., 'limit: 1-10000, default 20. Requesting > 1000 items may cause performance issues on large clusters.'
• Add field name mapping in descriptions where Kubernetes domain terms differ from parameter names. E.g., 'resourceType refers to the Kubernetes resource kind (e.g., Pod, Deployment, Service).'

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

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