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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered by structured data. The description adds the irreversible-permanence emphasis and a mandatory user-confirmation step, which is real behavioral value, but it says nothing about whether a non-empty cluster can be deleted, what happens to dependent resources, or error behavior.

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 zero filler, and the destructive consequence is front-loaded before the procedural instruction. Slightly clipped phrasing ("for good") is informal but still clear.

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 tool with full schema coverage and strong annotations, the description covers the essentials: what it destroys, that it is irreversible, and that confirmation is required. Missing only edge-case behavior around cluster state and dependency handling.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the id comes from list_clusters or create_cluster. The description adds no additional meaning about the cluster argument, so the baseline 3 applies.

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 cluster") with a permanence qualifier, which is unambiguous against siblings like get_cluster, rename_cluster, or create_cluster. It does not explicitly name an alternative, but no plausible confusion exists for a delete operation.

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 supplies one concrete usage rule — confirm with the user first — which is genuinely useful for a destructive action. It gives no explicit when-not conditions or pointers to alternatives (e.g., remove contents via extract_from_cluster first), leaving preconditions to inference.

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