Check Kubernetes manifests

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavior: custom resources resolved via their CRD, multi-document support, and that findings carry file, line, and fix. It stops short of stating whether results are exhaustive or how severity is ordered, but the added context is substantial.

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?

Dense but front-loaded, leading with what is checked before the qualifications. It's a single long sentence fragment chain with no wasted preamble, though the list-like packing is slightly denser than needed.

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 spelled out, yet the description still notes the shape of findings. Coverage of inputs, defaults, validation scope, and the Helm/Kustomize prerequisite makes this complete for a read-only checker.

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?

With 67% schema coverage, the description compensates well: it explains kubernetes_version defaults to the newest release, describes the pod_security levels and that their violations become errors, and clarifies that files must be rendered (Helm/Kustomize) before passing. This adds meaning beyond the raw schema fields.

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?

States a specific verb (checks) and resource (Kubernetes manifests) plus the scope of what is validated: removed/deprecated APIs, unknown fields, API server refusals, Pod Security, and risks. The sibling tools (api_versions, field_help) are clearly different in function, so an agent can route correctly without opening a schema.

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?

Gives concrete operating conditions: multi-document YAML/JSON, Kubernetes version defaults to newest, Pod Security baseline by default and restricted on request, and a prerequisite to render Helm/Kustomize first. It doesn't name alternatives or explicit when-not cases, but the context is clear enough to invoke confidently.

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