list_terminating_pods

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

With no annotations, the description should disclose what the tool does behaviorally. It explains the exact filter condition for terminating pods (deletion_timestamp set), which is useful. However, it does not disclose details about namespace/cluster scoping, read-only nature (though 'List' implies it), or any potential edge cases. It is adequate but not rich.

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 two sentences, with the action verb in the first and a precise definition in the second. No filler or redundant details.

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?

For a simple list tool with an output schema, the description covers the core purpose and filter definition. However, it omits any explanation of the two optional parameters (namespace, cluster_alias), relying entirely on the schema defaults. This leaves some ambiguity about cluster-wide vs per-namespace listing, but overall the essence is captured.

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 provides no descriptions for either parameter (0% coverage), and the description does not mention namespace or cluster_alias at all. Defaults are shown in the schema, but the meaning and scope of these parameters are left entirely to inference. This is a significant gap.

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 'List pods stuck in Terminating state' – a specific verb and resource with a specific filter. It further defines the filter criterion precisely ('a pod is considered terminating if it has a deletion_timestamp set'), distinguishing it from sibling tools like list_pods or list_failing_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 the criterion that defines terminating pods, which implies when you would want this tool (when you suspect pods are stuck terminating). However, it does not explicitly mention alternatives or when not to use it, such as using force_delete_pod for cleanup or list_pods for all pods.

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