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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, but the description adds substantial context beyond them: it is an allowlist, not a shell; it cannot exec, apply, patch, scale, drain or delete anything other than one named pod; it accepts no label selector on the delete path; a mistaken confirmation costs at most one pod; it changes production and requires confirmation. This is unusually rich disclosure.

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 description is long but front-loaded with purpose and exclusions, and every sentence carries necessary weight for a destructive multi-verb recovery tool: verb routing, the read-first warning, the allowlist constraint, and the confirmation requirement. No padding or repetition of structured data.

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, non-idempotent cluster-recovery tool with no output schema, the description covers purpose, per-verb usage, behavioral constraints, confirmation requirements, and availability exclusions. An agent has everything needed to decide whether and how to call it.

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%, so the schema already documents all 8 parameters including the verb enum and its per-value meaning. The description's verb guidance is really usage routing rather than parameter semantics, and it adds no syntax or format detail beyond what the schema provides. The baseline of 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?

The description names a specific verb and resource ('Run one allowlisted STATE-CHANGING kubectl command') and scopes it precisely ('inside an Ankra-provisioned cluster ... from a control-plane node over SSH-via-bastion'). It clearly distinguishes itself from siblings by naming ssh_kubectl_read as the prerequisite diagnostic and by explaining that the in-cluster agent is offline, so no other path exists.

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?

It gives explicit when-to-use guidance per verb (e.g. rollout_restart for a healthy ReplicaSet that never checks in; rollout_undo for a bad self-upgrade; delete_pod for stuck Terminating pods), names the alternative (ssh_kubectl_read) and the condition selecting it, and states exclusions ('Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus').

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