k8s_list_namespaces

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List namespace names' and does not mention whether a connection is required, whether it returns an error if not connected, whether it is read-only, or any pagination/format details. For a tool with zero annotation coverage, this is a significant gap.

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 short sentence, which is appropriately concise for a simple list operation. It is front-loaded with the verb and resource. However, it is so terse that it omits useful context, so it earns a 4 rather than a 5.

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 tool has an output schema and only one optional parameter, the description is mostly adequate for a trivial list call. However, with no annotations and no mention of session/connection requirements, an agent may not know whether it needs to call k8s_connect first or how session_name affects the result. The output schema covers return values, but the missing behavioral context lowers the score.

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 0%, so the description must compensate for the undocumented 'session_name' parameter. The description does not explain what session_name means or how it affects the listing. However, the parameter has a default and is not required, so the baseline is slightly higher; still, the description adds no semantic value beyond the 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?

The description 'List namespace names' clearly states the verb (list) and resource (namespaces), and specifies that it returns names rather than full details. It is distinguishable from sibling tools like k8s_list_pods or k8s_list_deployments, though it does not explicitly name a sibling 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 description implies usage: call this when you need namespace names. It does not explicitly state when to use it versus alternatives, nor does it mention prerequisites like needing an active session (k8s_connect). The context is clear enough for a simple list operation, but there is no explicit guidance.

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