k8s_list_configmap

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

No annotations are present, so the description carries the full burden. It describes the tool as listing ConfigMaps with key names, which implies a read-only operation, but lacks details on behavior such as pagination, error handling, or permissions required.

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 extremely concise with two short sentences, each providing essential information without any fluff. Every word adds value, and the most important action (listing) 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?

For a simple list tool with 3 parameters and no output schema, the description covers the main behavior and parameter usage. It could mention that only key names are returned (not values) or that the output is a list of ConfigMap objects, but it is largely adequate.

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%, but the description adds meaning for 'label_selector' (filtering) and 'namespace' (omit for all namespaces). However, it does not explain the required 'context' parameter, leaving its purpose unclear. The description partially compensates for the schema gap.

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 states exactly what the tool does: list Kubernetes ConfigMaps with their key names. It uses a specific verb 'List' and resource 'ConfigMaps', distinguishing it from sibling tools like k8s_get_configmap_detail which retrieves a single detailed ConfigMap.

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 provides clear usage guidance: 'Use label_selector to filter' and 'Omit namespace for all namespaces'. This helps the agent decide when to set these parameters, but does not explicitly compare to alternatives like k8s_list_secret or k8s_get_configmap_detail.

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