Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and error handling guidance. list_resources and get_resource have good descriptions (100+ chars) and proper input schemas with types. kubectl tool lacks parameter descriptions entirely, the 'args' parameter has no guidance on valid kubectl commands or error recovery. No tool descriptions explain error cases, retryability, or recovery paths. Missing output schema documentation for all tools. Parameter descriptions are present but generic; none explain constraints, formats, or dependencies. No tool declares permissions or security implications despite kubectl being a WRITE operation.

• Add detailed parameter descriptions to kubectl: 'args: kubectl command arguments as list (e.g., ["get", "pods", "-o", "json"]). Valid commands: get, describe, logs, exec, port-forward, apply, delete. Avoid destructive commands without explicit confirmation.'
• Document output schemas for all tools. Example for list_resources: 'Returns {"items": [{"name": string, "kind": string, "namespace": string, "status": string}], "total": number}'
• Add enum constraints to 'kind' parameter: restrict to common K8s resource types (Pod, Deployment, Service, ConfigMap, Secret, StatefulSet, DaemonSet, Job, CronJob, Ingress, PersistentVolume, etc.) with validation.
• Add error handling guidance to all tool descriptions: 'If resource not found, returns error with available alternatives. If permission denied, check RBAC. If context invalid, call list_contexts() first.'
• Declare kubectl as destructive with confirmation pattern: 'This tool can modify or delete resources. For write operations (apply, delete, patch), consider using --dry-run=client first or requesting user confirmation.'

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

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