delete_pod

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

Annotations already carry destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is partly covered. The description goes beyond them by tagging '[WRITE][risk=medium]' and clarifying that deletion is not permanent because a controller usually recreates the pod, which is real context an agent needs. It stops short of permission/auth or return-value details.

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 write/risk tag and core action, then a structured Args block. Every sentence earns its place; the only minor redundancy is dry_run appearing both in prose and the Args list, which is acceptable for scannability.

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 4-parameter destructive tool with no output schema and 0% schema coverage, the description covers the action, the irreversibility caveat, the preview mechanism, and every parameter. It omits only permission requirements and return/pagination behavior, which are minor here.

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 full param burden, and it documents all four: name, namespace ('omit for the target's default namespace'), dry_run, and target ('k8s target name from config'). That meaningfully compensates for the empty schema, though the per-param text is terse.

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 ('Delete a pod') and adds a distinguishing behavioral note ('No undo — a controller usually recreates it'). An agent can tell this apart from delete_job or delete_deployment without opening either schema.

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 gives a preview workflow ('Pass dry_run=True to preview without deleting') which is useful, but it offers no guidance on when to delete a pod versus alternatives like drain_node or rollout_restart_deployment, nor any prerequisite or exclusion conditions.

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