kubectl_events

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

With no annotations, the description carries the full burden. It usefully discloses sort order (most recent first) and that the default is all namespaces, but says nothing about how many events are returned, any time window, result caps/truncation, or required permissions.

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?

A single front-loaded sentence with the core action, ordering, and scope; no filler or redundancy.

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, and both parameters are fully documented in the schema. The remaining gap is behavioral (result volume, time window) rather than structural, leaving it nearly complete for a simple list tool.

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 'cluster' and 'namespace' are already documented, including the default of all namespaces. The description restates the namespace scoping without adding syntax, format, or behavior beyond the schema; baseline 3 applies.

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 (List) and resource (Kubernetes events) plus the ordering guarantee ('most recent first') and scope ('optionally scoped to one namespace'). It is clearly distinguishable from kubectl_logs or kubectl_describe by resource, though it never names a sibling or contrast case.

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?

Usage is only implied: 'recent events' suggests troubleshooting/cluster-health triage, and the namespace scoping hints at a filtering workflow. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives like kubectl_describe or kubectl_logs for deeper diagnosis.

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