k8s_get_namespaces

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

No annotations are provided, so the description must disclose behavioral traits. 'List' implies a read-only, safe operation, which is adequate. However, it does not explicitly confirm idempotency, authorization needs, or whether the output is paginated. The description is not misleading but could be more transparent.

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 sentences covering purpose and usage, with no fluff. Front-loaded with the core action. Every word serves a purpose.

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 list tool with one parameter and no output schema, the description adequately covers the core functionality. It mentions the use case (discovery before querying), which fits with sibling tool context. Could be improved by noting that the context parameter refers to a kubeconfig context, but overall it's sufficient.

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 one parameter 'context' with no description; schema description coverage is 0%. The tool description adds nothing about this parameter. The agent only knows it's a required string. While 'context' is a common term in Kubernetes, the lack of any explanation leaves the agent guessing about its exact value or format.

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 clearly states the action 'List all namespaces in a Kubernetes cluster', which is a specific verb and resource. It also hints at its purpose as a discovery step before querying resources, helping distinguish it from other tools like k8s_create_ns or k8s_delete_ns, though not explicitly naming them.

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 gives one usage cue: 'Use this to discover available namespaces before querying resources.' This implies when to use it, but does not provide when-not-to or mention alternatives like k8s_get_contexts. Guidance is present but minimal.

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