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

Annotations already cover the safe read-only, non-destructive, idempotent nature. The description adds the `kubectl events` analogy, which helps the agent predict command-like behavior and output style. It does not contradict annotations and adds value beyond the structured fields.

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?

Two short sentences, with the primary purpose front-loaded and an illustrative analogy in the second. Every word earns its place; 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?

The output schema exists and the input schema fully documents parameters and defaults (e.g., limit 500, namespace default). The description is minimal but sufficient for a simple list operation. It could mention whether it supports cross-namespace or cluster-wide events, but that's already in the schema. The analogy to kubectl events adds practical context.

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 the schema fully documents all six parameters. The description adds no additional parameter semantics beyond the `kubectl` analogy, which only loosely implies filtering options. Baseline 3 is appropriate since the schema carries the load.

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 ('Retrieves') and resource ('events from a Kubernetes cluster'), clearly distinguishing it from sibling tools that retrieve logs, resources, or API resources. The analogy to `kubectl events` reinforces the tool's function.

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 implies use for fetching Kubernetes events via the `kubectl` analogy, but it does not explicitly state when to prefer this tool over alternatives like get_k8s_logs or describe_k8s_resource. There are no stated exclusions or alternative references, so guidance is only implicit.

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