K8S Events

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation via `kubectl get events`, but does not mention ordering, time windows, namespace selection, filtering, or any side effects/safety characteristics.

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 compact, front-loaded with the resource and scope, and contains no filler. The `kubectl get events` parenthetical is an efficient orienting detail, though the overall terseness contributes to under-specification elsewhere.

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?

Even with an output schema present, the description does not tell the agent how to specify cluster/namespace selection in `params`, what the default scope is, or how this tool relates to neighboring k8s tools. For a tool with a free-form parameters object, this is not enough to invoke it correctly with confidence.

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?

The input schema defines a single generic `params` object with `additionalProperties: true` and 0% schema description coverage. The description offers only a weak hint that cluster/namespace scoping is possible, but it never explains what keys or values `params` accepts, leaving invocation semantics largely ambiguous.

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 identifies the resource ('events') and scope ('cluster/namespace') and references the canonical `kubectl get events` command, making the purpose reasonably clear. It lacks an explicit imperative verb in the main text, but the resource name distinguishes it from sibling k8s tools.

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 provides no guidance on when to use this tool versus siblings like k8s_pods, k8s_logs, k8s_describe, or k8s_top. It only hints at cluster/namespace scope, with no conditions, exclusions, or alternative tool references.

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