Most tools target distinct resource/action pairs, and names like list_pods vs create_pod vs describe_pod are easy to distinguish. The only mild overlap is between describe_pod and get_logs, but their descriptions clarify the difference (status/containers vs logs).

The set mostly follows a clear verb_noun convention: list_pods, create_deployment, delete_pod, describe_pod, get_logs. The lone outlier is cleanup, which lacks a resource noun and breaks the pattern slightly.

With 11 tools, the server is well within the ideal 3–15 range for a scoped Kubernetes operations surface. Each tool maps to a recognizable kubectl-style operation without feeling bloated.

The surface covers listing several core resource types plus create/delete/describe for pods and create for deployments, but lifecycle coverage is uneven. There is no delete_deployment, no update/scale operation, no create_service, and no exec or configmap/secret handling, so agents will hit dead ends for common workflows.