list_pods

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

Describes a read-only operation listing pods, which is accurate. No annotations are provided, so the description carries the full burden. It does not discuss pagination or potential performance impacts, but for a simple list tool this is acceptable.

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, front-loaded with the primary action and output fields, followed by usage guidance. Every sentence adds value with no redundancy.

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 low complexity (one optional parameter, no output schema), the description fully covers what the tool does, returns, and when to use it. No missing information.

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 only parameter (namespace) is fully described in the schema (100% coverage). The description adds context by stating defaults to 'default', reinforcing the parameter's purpose.

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 tool lists all pods in a namespace with specific fields (name, status, restart count, age, node), distinguishing it from sibling tools like get_pod_logs or get_pod_status which focus on individual pods or different details.

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?

Explicitly advises using this as a first step to get an overview and spot problematic pods, providing clear context for when to use it. However, it does not explicitly mention when not to use or directly compare to siblings.

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