delete_pod

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

Reveals that deletion is not permanent (controller recreates) and mentions an allowlist, but does not disclose failure modes, permissions, or side effects on running containers. With no annotations, more detail would be beneficial.

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?

A single sentence that packs core purpose and outcome. Very concise, but could be slightly expanded to include parameter hints or use cases without losing efficiency.

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?

Provides essential purpose and behavioral effect, but lacks parameter descriptions, usage guidelines, and error states. Given absent annotations and unknown output schema, more context would be needed for robust agent usage.

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?

Parameters (namespace, name) are not explained in the description. While their names are conventional, the description adds no semantic context beyond the schema. With 0% schema coverage, 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?

Cleary states the action (delete) and resource (pod), with added behavioral outcome (controller recreates it) and constraint (allowlist). Distinguishes from siblings like restart_deployment.

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?

No explicit guidance on when to use this tool vs alternatives. The description implies a specific behavior but does not state conditions, exclusions, or compare to similar tools.

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