force_delete_pod

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

With no annotations, the description must carry the behavioral burden. It discloses grace_period_seconds=0 and the specific scenario, which adds context. However, it does not explain potential side effects, permission requirements, or irreversibility of force-deletion, leaving gaps in understanding the destructive nature.

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 concise sentences, front-loaded with the key action and use case. Every sentence earns its place with no wasted words.

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 tool is destructive with no annotations, no output schema, and undefined parameters. The description only covers when to use it, not what the outcome is or what the parameters mean. It feels incomplete for a force-delete 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 coverage is 0% and the description does not explain any of the three parameters. While the tool name and description imply that 'name' is the pod name, namespace and cluster_alias are left undefined. The description adds no parameter-level detail, so it does not compensate for the schema gaps.

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 tool force-deletes a pod stuck in Terminating state, with a specific verb ('Force-delete') and resource ('pod'). It does not explicitly differentiate from sibling tools like force_delete_all_terminating_pods, but the singular focus is clear.

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 second sentence provides explicit guidance: 'Use this when a pod will not terminate normally and is stuck.' This gives a clear use case, though it does not mention alternatives or exclusions. It is useful but not full when/when-not coverage.

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