iac_scan_k8s

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must carry behavioral disclosure. The verb 'Scan' reasonably implies a non-mutating analysis operation, but the description does not disclose whether files are scanned locally or sent externally, whether an API key is required for actual scanning, or what the output/report format is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. It directly conveys the action, target, and purpose, which is appropriately concise for this tool's scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and an undocumented optional parameter, this description is too thin. It does not explain return values, whether the scan is local or remote, the role of the API key, or how this relates to sibling tools like iac_fix_issues and k8s_security_audit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: 'directory' is documented, but 'api_key' has no schema description. The tool description itself adds no parameter-level meaning, so the agent is left to guess why an API key is needed and how it relates to scanning Kubernetes manifests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Scan') and a specific resource ('Kubernetes manifests') with a clear goal ('security misconfigurations'). It differentiates from sibling IaC scanners like iac_scan_terraform and iac_scan_docker, though it does not explicitly distinguish itself from the similarly-scoped k8s_security_audit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is appropriate for Kubernetes manifest scanning by naming that target resource, which gives some selection context against non-K8s IaC tools. However, it provides no explicit guidance about when to choose this tool over k8s_security_audit, iac_fix_issues, or other related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.