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. It explicitly discloses that namespaces outside the allowlist are filtered out—a non-obvious behavioral restriction for a list operation. It does not describe return formatting or pagination, but for a basic read-only list tool this is a meaningful behavioral disclosure.

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 carry all the information: a clear action in the first sentence and a key behavioral constraint in the second. There is no filler, and the most important information is front-loaded.

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's simplicity—a single optional parameter, no output schema, and no annotations—the description covers the essential purpose and a meaningful filtering restriction. It does not provide broader context about cluster access or when to branch to other tools, but it is sufficient for invoking this list operation correctly.

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%: the single 'context' parameter is already documented in the input schema as the kube-config context to target and its default. The tool description adds no parameter-specific details, so the baseline of 3 is appropriate.

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 the verb ('List') and the resource ('namespaces') with explicit cluster scope, and adds the allowlist-filtering behavior. This clearly distinguishes it from sibling tools like list_contexts, list_pods, and get_resource by resource type.

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 does not prescribe when to use this tool versus alternatives, nor does it mention list_contexts, get_namespace, or other resources. The only signal is the allowlist filter, which implies current-access-limited usage but gives no explicit when-to-use/when-not-to-use guidance.

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