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

Annotations only declare destructiveHint=true and idempotentHint=false; the description adds substantial context beyond that: nodes are terminated one at a time, each drained through its PodDisruptionBudgets first, a refused drain keeps the node and the group and the operation fails naming the refuser, workloads pinned to the group become unschedulable, and re-adding the same name yields fresh empty nodes. This is unusually rich behavioral disclosure for a mutation tool.

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 core action and scope, then layers consequences and the pre-call instruction. It is one very long semicolon-chained sentence, which is dense to parse, but virtually every clause carries information an agent needs.

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 tool with no output schema, the description covers failure semantics, partial-failure behavior, blast radius on workloads, and irreversibility. Nothing an agent needs before invoking it 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%, so cluster_id, group_name and cluster_name are already documented in the schema. The description only echoes the list_node_groups provenance of group_name, adding no new parameter-level semantics; 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 (delete) and resource (worker node group) plus the scope qualifier 'Ankra-provisioned self-managed cluster', which cleanly separates it from delete_managed_node_pool and delete_cluster. An agent can identify the target entity without opening the 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?

Gives an explicit prerequisite sequence ('Call list_node_groups first and confirm the group with the user'), which is exactly the workflow guidance an agent needs before a destructive call. It does not, however, contrast against sibling destructive tools such as delete_managed_node_pool or cordon_node/drain alternatives.

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