K8S Pods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a non-destructive listing and reveals that phases and restarts are included, but it does not mention cluster requirements, authentication, pagination, or behavior on large pod sets.

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 short, front-loaded phrase with no filler words. It is efficient, though so terse that it sacrifices useful context.

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 presence of an output schema covers return-value shape, but the description omits usage guidance, parameter semantics, and behavioral context. This is incomplete for a Kubernetes tool with many closely related siblings and a free-form parameters object.

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 schema has one generic free-form 'params' object with 0% description coverage, and the description adds no parameter semantics. An agent cannot infer how to filter by namespace, label selector, or other criteria.

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 states a specific verb and resource ('list pods') and names included output aspects (phases and restarts), which distinguishes it from Kubernetes siblings like logs, describe, and top. It is clear though it does not explicitly contrast itself with those 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?

No guidance is provided on when to use this tool versus alternatives such as k8s_deployments or k8s_top, nor on namespace/cluster context or filtering. The only usage signal is the verb 'list', which implies a read-only inventory operation.

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