k8s_list_secret_names

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

Since no annotations are provided, the description must carry the full behavioral disclosure burden. It does disclose one important behavior: values are not returned, which signals a non-sensitive read operation. However, it does not mention connectivity, permission requirements, empty-result behavior, or pagination, leaving notable gaps.

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 two short, front-loaded sentences with no filler. The core behavior is stated immediately, and every word earns its place, though it is arguably too sparse to carry the context needed for correct invocation.

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?

With an output schema present, the return shape does not need to be explained, but the description still omits meaning for namespace and session_name. An agent cannot be certain whether an empty namespace means current namespace, all namespaces, or default namespace, and session_name's role is entirely unexplained.

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%, and the description does not mention namespace or session_name at all. The agent receives no explanation of what an empty namespace means, whether namespace is required for scoping, or what session_name refers to.

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 uses a specific verb and resource: 'List Secret names only.' It also adds the valuable distinction that values are not returned, making the tool's scope unambiguous even among the sibling k8s tools.

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?

There is no when-to-use guidance, no mention of alternatives, and no prerequisites such as requiring an active k8s connection. The phrase 'names only' weakly implies a lightweight use case, but the agent is not told when this tool should be preferred over other listing or secret-related operations.

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