Two tools with minimal descriptions and incomplete parameter documentation. list_resources has a 73-char description (acceptable baseline ~194 chars); get_resource_yaml has 77 chars. Neither tool has parameter descriptions visible in the schema. Input schemas present but lack parameter-level descriptions required by pattern:tool-description. No output schema documented. No error handling guidance. Tools are read-only (low risk) but lack LLM-optimization for agent selection.

• Add parameter descriptions to both tools. For 'kind', explain: 'Filter resources by Kubernetes Kind (e.g., Deployment, Service, ConfigMap). If omitted, returns all kinds.' For 'namespace', explain: 'Kubernetes namespace. Defaults to "default" if resource has no namespace specified.'
• Expand tool descriptions to 100-200 chars. Example for list_resources: 'List all Kubernetes/GitOps resources in the local repository, grouped by Kind. Returns resource names, namespaces, and file paths. Call this first to discover available resources before fetching specific YAML.'
• Document output schema. For list_resources, specify: 'Returns object with keys by Kind (e.g., {"Deployment": [{name, namespace, filePath}, ...], "Service": [...]}). For get_resource_yaml, specify: 'Returns {yaml: string, filePath: string, kind: string, name: string, namespace: string}'.
• Add error handling guidance. E.g., 'If resource not found, returns error with available resources in the namespace. If YAML is malformed, returns parse error with line number.'
• Consider adding a 'format' parameter to get_resource_yaml (enum: 'yaml', 'json') to increase utility without adding a new tool. Document the parameter and its effect on output.