List Kubernetes Clusters

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

No annotations exist, so the description carries the full behavioral burden and it does not meet it. It never discloses that the listing is time-scoped, despite six window parameters (from/to/around/window/startDate/endDate) and allowLongRange, nor does it mention auth/connection selection behavior, result shape, or ordering.

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 resource and the sequencing instruction front-loaded; every clause carries information and nothing is padded.

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 read-only listing with a fully documented schema and no output schema, the description covers purpose and sequencing adequately. The gap is that it omits any explanation of the time-range parameters' role in a 'list clusters' call, which an agent may find counterintuitive.

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 all eight parameters are already documented in the schema, establishing the baseline of 3. The description adds only the k8s.cluster.name field reference and no additional parameter semantics such as default window behavior.

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 and resource ('List Kubernetes clusters') and pins the domain attribute it enumerates (k8s.cluster.name), so it reads clearly against sibling list tools like list_pods/list_nodes. It does not explicitly contrast itself with those siblings, but the cluster-level scope is unambiguous.

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?

'Call this before filtering pods' gives an explicit sequencing rule and makes the parent-child relationship with the pod tools clear. There is no statement of when not to use it or of alternative paths, but the guidance is concrete rather than implied.

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