list_pods

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention pagination, result limits, permission requirements, or sorting. The description only lists the output columns. This leaves significant gaps in understanding the tool's behavior.

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 concise, front-loading the core purpose in the first sentence. The parameter block is clean and uses no unnecessary words. Every sentence adds value.

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 tool outputs an array of objects (as inferred from output schema presence), the description lists key columns, which is helpful. However, it could mention pagination or maximum results for completeness. The need for alternative guidance (e.g., vs run_oc_command) is noted but not critical.

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 parameter descriptions (e.g., namespace: 'empty = all namespaces', label_selector: 'e.g. "app=nginx"') add meaningful context beyond the schema, which only has types and defaults. However, the schema coverage is 0%, so these explanations are essential and well done.

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's purpose: listing pods with specific columns (NAMESPACE, NAME, STATUS, etc.). It distinguishes it from siblings like get_pod (single pod) and other listing tools.

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 explains parameters and default behavior (e.g., empty namespace for all namespaces), but does not explicitly mention when to use this vs alternatives like run_oc_command or get_pod. No when-not guidance is provided.

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