Review Kubernetes Security

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds genuine non-redundant context by asserting it 'analyzes supplied YAML only and does not connect to a cluster,' which clarifies that no live cluster state is consulted. It stops short of describing output shape or any limits on manifest size, so not a full 5.

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 sentences with no filler: scope first, routing second, boundary condition last. Every sentence carries distinct information and the most decision-relevant content is front-loaded.

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?

With an output schema present, return values need not be explained, and annotations carry the safety profile. The description supplies the remaining gaps an agent needs: the exact analysis scope, the sibling it competes with, and the fact that it is purely static over supplied YAML.

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 100%, so both manifestYaml and environment are already documented in the schema, and the environment enum values are self-explanatory. The description adds no syntax, format, or interpretation guidance for either parameter, so the baseline 3 is appropriate.

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 verb+resource ('Apply Kubernetes workload security rules to manifest YAML') and enumerates the concrete rule categories covered (privileged mode, host access, capabilities, service accounts, seccomp, filesystem, network policy). It explicitly names the sibling review_kubernetes_deployment as the contrasting tool, so an agent can disambiguate without opening either 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?

It gives an explicit routing rule: 'Use this for security hardening; use review_kubernetes_deployment for reliability and production-readiness checks.' Both the when-to-use and the alternative with its selection condition are stated.

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