📋 Prerequisites
🎯 Affected Service(s)
Multiple services / System-wide issue
🚦 Impact/Severity
No impact (Default)
🐛 Bug Description
It seems that the descriptions of the apply_manifest and create_resource in python/src/kagent/tools/k8s/_kubectl.py unintentionally mislead the agent:
-
apply_manifest description: "Create a resource in Kubernetes. Must be a local file." Based on the implementation, it looks like the file doesn't need to be local. In my tests this consistently confused the agent when asked to apply a resource.
-
create_resource description: "Apply a YAML resource file to the Kubernetes cluster." This seems to have a similar issue as apply_manifest
Changing these to "Apply a YAML resource to the Kubernetes cluster." and "Create a resource in Kubernetes." greatly improved the model's ability to use tools in my tests.
Please let me know if I am missing something.
🔄 Steps To Reproduce
- Create an agent using qwen3:30b-a3b through ollama with the ApplyManifest and/or CreateResource k8s tools.
- Ask the agent "show me an example of a nginx pod"
- Then ask "apply the nginx pod to my local kubernetes cluster"
🤔 Expected Behavior
The agent calls either the create_manifest or the ApplyManifest or CreateResource tools with the manifest provided earlier as argument.
📱 Actual Behavior
The agent calls the ApplyManifest or CreateResource tools using a non existent 'nginx-pod.yaml' string as the argument, possibly being misled by the tool's description.
💻 Environment
No response
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?
📋 Prerequisites
🎯 Affected Service(s)
Multiple services / System-wide issue
🚦 Impact/Severity
No impact (Default)
🐛 Bug Description
It seems that the descriptions of the
apply_manifestandcreate_resourceinpython/src/kagent/tools/k8s/_kubectl.pyunintentionally mislead the agent:apply_manifestdescription: "Create a resource in Kubernetes. Must be a local file." Based on the implementation, it looks like the file doesn't need to be local. In my tests this consistently confused the agent when asked to apply a resource.create_resourcedescription: "Apply a YAML resource file to the Kubernetes cluster." This seems to have a similar issue asapply_manifestChanging these to "Apply a YAML resource to the Kubernetes cluster." and "Create a resource in Kubernetes." greatly improved the model's ability to use tools in my tests.
Please let me know if I am missing something.
🔄 Steps To Reproduce
🤔 Expected Behavior
The agent calls either the create_manifest or the ApplyManifest or CreateResource tools with the manifest provided earlier as argument.
📱 Actual Behavior
The agent calls the ApplyManifest or CreateResource tools using a non existent 'nginx-pod.yaml' string as the argument, possibly being misled by the tool's description.
💻 Environment
No response
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?