force_delete_all_terminating_pods

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

With no annotations, the description does not disclose the destructive consequences, lack of reversibility, or potential cluster impact. It simply restates the action from the tool name without adding behavioral context or safety warnings.

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, front-loaded sentence that efficiently conveys the core operation. No extra words, but it may be too terse given the need for safety and parameter 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?

As a bulk destructive tool with no annotations, output schema, or parameter descriptions, the description is insufficient. It tells the agent what it does but not the risks, prerequisites, or return behavior, making it incomplete for safe 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 0%, and the description does not explain the namespace or cluster_alias parameters, their defaults, or how they affect execution. The description fails to compensate for the lack of schema documentation.

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 action (force-delete), the resource (pods), the scope (ALL), and the condition (stuck in Terminating state) within a namespace. It distinguishes from sibling tools like force_delete_pod (singular) and list_terminating_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 implies usage when pods are stuck in Terminating state, but does not explicitly contrast with force_delete_pod for individual pods or provide warnings about bulk deletion. It gives a clear context but no exclusions or alternatives.

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