delete_pod

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

No annotations are present, so the description must carry behavioral disclosure. It explicitly flags permanence and enumerates three consequences of deletion (container, volume, tunnel), which is strong transparency for a destructive tool. It could additionally note irreversibility or permission requirements, but it already exceeds a bare 'Deletes a pod'.

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 entire description is a single efficient sentence that front-loads the action ('Permanently delete a pod') and only then specifies artifacts affected. Zero filler or duplication.

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 one-parameter destructive operation with no output schema, the description gives enough to invoke it correctly: what action, what objects are affected, and permanence. It stops short of stating error/return behavior or permission prerequisites, but those are secondary for this simple tool.

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%, so the description should compensate for the undocumented `name` parameter; it does not mention the parameter directly. The meaning is inferable from 'delete a pod' and the schema's `name` property, but the description adds no explicit parameter guidance.

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?

Description uses a specific verb phrase 'Permanently delete a pod' followed by the concrete scope of destruction ('removes its container, volume, and tunnel'). This clearly distinguishes it from sibling tools like get_pod/list_pods, which inspect, and manage_pod, which suggests modification.

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 makes the usage context evident: call this when a pod must be permanently removed, not merely stopped or managed. It does not explicitly name alternatives or state when-not-to-use (e.g., 'use manage_pod for reversible actions'), so it falls short of a full routing explanation.

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