k8s_events

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does disclose the result limit ('latest 30') and the event scope ('namespaced'). However, it does not mention prerequisites like an active session, how the namespace default behaves, or other operational details. No contradiction with annotations exists because none exist.

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 a single, tightly worded sentence that front-loads the key facts: action, resource, count, and scope. There is no redundant or filler content.

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?

Although the tool is simple and has an output schema, the description omits meaningful guidance about the two optional parameters and does not explain the session context. With no annotations and no parameter documentation, the agent cannot fully determine default behavior or edge cases.

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%, and the description must compensate by explaining the parameters. It only hints at 'namespace' via the word 'namespaced' and says nothing about session_name or how defaults are used. This is insufficient for an agent to confidently choose parameter values.

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 uses a specific verb ('Show'), a clear resource ('events'), and concrete scope details ('latest 30', 'namespaced'). This distinguishes the tool from sibling tools like k8s_list_pods or k8s_pod_logs, whose purposes clearly differ.

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 intended use is implied by the description: call this to view recent namespaced events. However, it provides no explicit guidance on when to prefer this tool over alternatives or any conditions that should trigger its use, leaving the usage context only implicit.

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