list_pods

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

With no annotations provided, the description must fully disclose behavioral details, but it only states the basic operation. It does not mention permissions, pagination, limitations of namespace scope, or how cluster_alias affects results, so the agent is left unaware of potential side effects or constraints.

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, succinct sentence that is immediately clear and front-loaded with the action and scope. It contains no wasted words and is appropriately sized for the tool's simplicity.

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?

While the tool is straightforward and an output schema exists to define return values, the description lacks important usage and behavioral context. It is minimally sufficient but incomplete, especially regarding cluster_alias and when to use the tool relative to siblings.

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 input schema has 0% description coverage, and the tool description fails to explain the parameters. It merely echoes 'namespace' without adding semantic meaning, and does not address cluster_alias at all, leaving the agent without necessary parameter context.

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 a specific action ('List') and resource ('Pods') with scope ('in a namespace'), making it easily distinguishable from filtered pod-listing siblings like list_failing_pods or list_pods_not_ready, as it explicitly says 'all Pods'.

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, such as filtered pod lists or get_pod. It does not mention use cases, exclusions, or prerequisites, leaving the agent without clear decision criteria.

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