get_cluster_events

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

Explicitly declares it is a read-only query and describes the return format (up to 50 events, including type, target, reason, message). Since no annotations are provided, this full disclosure is valuable.

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 concise, well-structured into purpose, usage, and behavior sections. Every sentence adds value without 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?

For a simple read-only tool with two optional parameters, the description is complete. It provides the resource, purpose, output format, and usage conditions, which is sufficient for an agent to call it correctly.

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 schema descriptions already fully cover both parameters (namespace and warning_only) with clear explanations. The tool description adds no additional semantic meaning beyond the schema, so the baseline of 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?

Clearly states the tool retrieves Kubernetes cluster events for diagnosing scheduling failures, node pressure, or eviction warnings. This distinguishes it from sibling tools like list_pods or get_pod_logs.

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?

Gives explicit guidance: call this tool when pods are stuck in 'Pending' or 'CrashLoopBackOff' states. It also suggests using warning_only to filter noise, providing practical usage context.

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