k8s_list_secret

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

Discloses that values are hidden for security, which is critical behavioral info. No annotations provided, so description carries the burden. Lacks mention of pagination, performance limits, or required permissions.

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 concise sentences, first states purpose and key security behavior, second provides usage tips. No unnecessary words, front-loaded with critical info.

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 no output schema and 3 parameters, description covers purpose, security, and two parameter hints. Could mention output format or structure, but overall provides enough context for a simple list tool.

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 coverage is 0%, so description must compensate. It explains label_selector with example and implies namespace semantics, but does not describe the required 'context' parameter. Adds some meaning beyond schema but not fully comprehensive.

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?

Description clearly states it lists Kubernetes Secrets and hides values for security. It specifies resource and action, but does not explicitly differentiate from other list tools like k8s_list_configmap or sibling k8s_get_secret_detail, though the mention of keys-only and hidden values provides some distinction.

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?

Provides guidance on using label_selector with an example and notes that omitting namespace lists across all namespaces. However, it does not indicate when to use this tool versus k8s_get_secret_detail or other alternatives, nor does it specify prerequisites like permissions.

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