docs: Update getting-started to use per-operation Docker tools

Switch from unified 'docker' tool to specific per-operation tools for:
- Better token efficiency (no need to construct command strings)
- More accurate execution (tools have built-in safety like --no-stream)
- Structured outputs (JSON instead of raw text)
- Clear tool descriptions guide the LLM

Tools used:
- docker_ps: List containers
- docker_stats: Resource usage (with --no-stream built-in)
- docker_logs: View logs
- docker_images: List images
- docker_exec: Execute commands

This approach is recommended for production agents as it reduces
errors and improves reliability.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: gouravjshah

docs/getting-started.md

@@ -65,19 +65,21 @@ spec:
     You are a Docker health checker. Help users understand what's
     running in their Docker environment.
 
-    Use docker commands to check container status, view logs,
-    and explain any issues you find.
-
-    IMPORTANT: When using 'docker stats', ALWAYS add the --no-stream flag
-    to get a one-time snapshot. Without it, the command runs continuously
-    and will timeout.
-
-    Example: "docker stats --no-stream" or "docker stats --no-stream --all"
+    Available tools:
+    - docker_ps: List running containers
+    - docker_stats: Get resource usage (CPU, memory, I/O)
+    - docker_logs: View container logs
+    - docker_images: List images
+    - docker_exec: Execute commands in containers
 
     Keep responses concise and actionable.
 
   tools:
-    - docker
+    - docker_ps
+    - docker_stats
+    - docker_logs
+    - docker_images
+    - docker_exec
 ```
 
 ### Run It