Delete Pod

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

Goes well past the annotations by spelling out consequences: attached network storage survives while hostPath volumes are destroyed only when named in delete_local_storages. It also documents the operation_id lifecycle and prescribes checking operation_status and resource state after a timeout before retrying — exactly the retry-safety context annotations cannot convey.

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?

Front-loaded with the destructive action, then the confirm protocol, then storage side effects, then the operation_id contract — a sensible ordering. The operation_id paragraph is slightly boilerplate-heavy but each sentence carries distinct retry or idempotency information.

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?

An output schema exists so return values need no explanation, and the description fills the remaining gaps: preview semantics, selective volume deletion, and timeout recovery. An agent could execute this safely without consulting anything else except the pod/workspace parameter meanings.

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%, so the description carries the burden, and it does so for three of five parameters: confirm's preview semantics, delete_local_storages' pv_name matching, and operation_id's reuse rules. The `pod` and `workspace` parameters remain unelaborated, leaving a small 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?

States a specific verb and resource plus a scope qualifier ('permanently'), and the preview/confirm framing makes clear this is the destructive end-state operation. It does not explicitly contrast itself with the obvious sibling stop_pod, leaving the permanence-vs-suspend distinction to be inferred.

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?

Gives an explicit call sequence: preview with confirm=false, obtain user agreement, then re-call with confirm=true. That is clear operational guidance. It stops short of naming alternatives (stop_pod for reversible shutdown) or stating when deletion should not be attempted at all.

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