k8s_pod_list

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

No annotations are provided. The '[SAFE]' tag implies read-only, but the description does not explicitly disclose behavior like auth requirements or rate limits. For a listing tool, the default behavior is safe, but more detail could be helpful.

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 sentence that conveys the essential information without any fluff. It is well-structured and front-loaded with the safe tag and main action.

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?

The description mentions 'status and metadata' as return values, but with no output schema, more detail would help. It does not address pagination or list size limits, which are common for Kubernetes APIs.

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%, meaning the description adds no meaning beyond the parameter names. The single parameter 'namespace' is not described in the text, so the agent must rely solely on the schema.

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 clearly states the action (list), resource (Kubernetes pods), and scope (in a namespace). It distinguishes from sibling tools like k8s_deployment_list and k8s_node_list.

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. While the tool is straightforward, it misses an opportunity to specify context or exclusions.

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