k8s_list_pods

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

No annotations are provided, so the description must bear the burden of behavioral disclosure. 'List' implies a read-only operation, but the description omits details about pagination, required permissions, or output format. It is adequate but not thorough.

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, ultra-concise sentence. While it contains no filler, it is too minimal to fully convey the tool's capabilities and lacks structured information such as usage hints or examples.

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 absence of an output schema and the simplicity of the operation, the description should at least hint at the return format (e.g., list of pod objects) to aid agent understanding. The current description is incomplete for a tool with two optional parameters and no other documented behavior.

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?

The input schema covers both parameters (namespace, labelSelector) with descriptions and defaults, achieving 100% coverage. The description adds no additional semantic context beyond what the schema already provides, meeting the baseline.

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 Kubernetes pods' clearly indicates the action (list) and resource (pods). It is specific enough to convey the tool's purpose, though it does not explicitly differentiate from sibling tools like 'k8s_get_services' or 'docker_list_containers'.

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 no guidance on when to use this tool versus alternatives such as 'k8s_get_services' or when filtering is appropriate. It lacks any context about suitable scenarios or prerequisites.

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