kubectl_get_pods

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

No annotations are provided, so the description carries the full disclosure burden. 'List' implies a safe, non-mutating read, which is the key behavioral fact for this tool, but it says nothing about authentication/credential requirements, whether the query is cluster-wide by default affecting cost/latency, or pagination 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?

A single front-loaded sentence with the resource stated first and the scope qualifier second. Nothing is wasted, though the trailing clause largely echoes the namespace parameter's own schema description.

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?

An output schema exists, so return values need not be explained, and the tool is a simple two-parameter read with full schema coverage. The remaining gap is environmental context (which cluster/credential the agent must supply and default cluster-wide behavior), which is minor for a list operation.

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 100%, and both parameters are already documented (cluster name, namespace with 'default: all namespaces'). The description only restates the namespace scoping and adds no format or syntax detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('List pods in a Kubernetes cluster') plus an explicit scope modifier (optional namespace). This clearly separates it from sibling kubectl tools like kubectl_nodes, kubectl_logs, and kubectl_describe, though it never names those siblings explicitly to sharpen the boundary.

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 optional-namespace phrasing implies when to narrow the query, but there is no explicit guidance on when to use this versus kubectl_describe, kubectl_events, or kubectl_logs, nor any stated prerequisites (cluster credentials/context). Usage is inferable from the resource name rather than stated.

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