websex_kube_hunter

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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior: kube-hunter is executed directly with argv tokens and shell parsing is never used, and it runs from the engagement namespace. However, it says nothing about permissions/auth needs, whether the scan is active/intrusive against the target cluster, rate limits, or side effects — significant gaps for a security scanning tool.

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?

Three short sentences, front-loaded with the execution model, and no filler. It is appropriately sized for a wrapper tool, though the third clause (relative paths) is a little tacked-on.

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?

An output schema exists, so return values need not be described. But for a 4-param tool with 0% schema coverage and no annotations, the description leaves the agent without the tool's actual purpose, the meaning of engagement_id, or any selection guidance against near-identical siblings. Adequate but with clear gaps.

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 0% across 4 parameters. The description gestures at two of them obliquely ('supplied argv tokens' → arguments, 'use relative paths for engagement artifacts' → working_directory) but never explains engagement_id or stdin, and gives no format, constraints, or defaults. It only partially compensates for the coverage gap.

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?

"Run kube hunter" mostly restates the tool name and adds only the container/toolkit location; it never states what kube-hunter actually does (hunt for security weaknesses in a Kubernetes cluster) nor how it differs from the adjacent websex_kube_bench sibling. The operational framing ('WebSex cloud container iac toolkit') adds a little context but also arguably mislabels a k8s pentest tool as IaC tooling.

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?

No when-to-use guidance and no alternatives named, despite a crowded field of overlapping siblings (kube_bench, docker_bench, trivy, checkov, terrascan). The only conditional content is about relative paths for artifacts, which is a usage constraint, not tool selection guidance.

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