get_cluster_health

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

No annotations are provided, so the description carries the behavioral burden. It does convey that this is a read-only health query and names the metric categories included. Yet it does not clarify aggregation semantics, whether the data spans all namespaces, or whether it is a current snapshot, leaving some behavioral ambiguity.

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 front-loaded sentence with no filler. Every clause supplies a distinct piece of information about the tool's scope and outputs.

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 no-parameter tool with an output schema, the description covers the core purpose and the categories of returned health data; the output schema can handle detailed return formatting. The main missing piece is explicit differentiation from sibling observability tools, but the 'overall' scope makes the tool's role reasonably clear.

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 has zero parameters, so there is no parameter meaning for the description to add beyond the 100% schema coverage. With 0 parameters, the baseline is 4, and the description appropriately avoids adding unnecessary parameter details.

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 names a specific verb ('Get'), a clear resource ('overall Kubernetes cluster health'), and enumerates concrete output categories (node count, pod status, CPU/memory utilization). The word 'overall' helps separate it from the more targeted sibling tools, though it does not explicitly reference an alternative.

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 'overall' wording implies this tool is for a high-level health summary rather than the focused checks performed by siblings like get_pod_metrics or get_node_pressure. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are named.

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