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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: a controller-managed pod will be recreated automatically, meaning the call is effectively a restart in that case. It does not mention that termination is asynchronous or subject to the grace period, but it exceeds the annotation baseline.

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?

Two short sentences with no padding; the core action is front-loaded and the consequence clause follows immediately. Every sentence earns its place.

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 destructive Kubernetes operation with full annotation coverage and full schema coverage, the description supplies the one behavioral fact an agent most needs (controller-managed pods reappear). It omits any note about dry_run previewing or the asynchronous/grace-period nature of termination, which would be useful for a destructive call, but nothing critical to correct invocation is missing.

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 100% for all five parameters (including dry_run and grace_period_seconds), so the schema already carries parameter meaning. The description adds nothing beyond it — baseline 3 is appropriate.

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+resource ("Delete a specific pod") that is unambiguous about the operation. It does not, however, distinguish itself from other destructive siblings in the fleet (delete_resource, delete_application, restart_deployment), so it lands at 4 rather than 5.

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?

Usage is only implied by the operation name; there is no explicit statement of when to delete a pod versus restart_deployment or ssh_kubectl_recover, and no preconditions (e.g., that deleting a bare pod is unrecoverable while a controller-managed pod is not). The controller caveat hints at consequences but not at selection criteria.

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