List kube-config contexts

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

With no annotations, the description carries the burden of behavior. 'List' clearly indicates a read-only operation with no side effects, which is sufficient for this simple tool. However, it does not disclose behavior such as what happens if no kube-config is loaded or if the output is just names.

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?

A single, compact sentence that adds value beyond the tool name by specifying 'contexts (clusters)' and 'loaded kube-config'. No fluff or unnecessary details.

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?

Given the zero-parameter schema, no output schema, and clear listing semantics, the description is complete. An agent can correctly determine when and how to invoke this tool without additional information.

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 nothing to clarify. The description correctly refers to the existing kube-config as the only implicit input, which matches the 0-parameter schema.

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?

States a specific verb ('List'), a clear resource ('contexts (clusters)'), and a source ('loaded kube-config'). It is clearly distinguishable from sibling resource-listing tools like list_namespaces or list_pods.

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 when it should be used: whenever the agent needs to know which kube-config contexts are available. It does not explicitly name alternatives or when-not-to-use cases, but the scope is clear enough for a zero-parameter listing tool.

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