k8s_delete_kubernetes_node

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

No annotations are present, so the description carries the burden of behavior disclosure. It states the destructive action and return value, and the 'smart identifier resolution' note adds useful behavior beyond the schema. However, it does not disclose irreversibility, permissions, or the impact on workloads running on the node, which are relevant for a delete operation.

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 compact and logically structured with an Args/Returns layout. It avoids boilerplate, though the 'ctx' line adds little for an agent and the 'smart identifier resolution' sentence could arguably be merged with the Args descriptions.

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 three-parameter destructive tool with no annotations, the description provides the essential identifiers and return message, and the output schema exists. It is missing consequences such as permanence and workload disruption, as well as alternative-tool guidance, so it is minimally adequate rather than fully complete.

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?

The input schema has 0% description coverage, but the Args section compensates by explaining each identifier parameter as 'label or ID'. This gives real semantic meaning beyond the bare string fields. The inclusion of a non-schema 'ctx' argument is slightly confusing, but all three actual parameters are adequately described.

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 first sentence, 'Delete a specific node from a node pool,' names a specific verb, resource, and scope. This clearly distinguishes the action from sibling tools like k8s_delete_kubernetes_node_pool and k8s_recycle_kubernetes_node.

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?

There is no guidance on when to choose this tool over alternatives, such as k8s_recycle_kubernetes_node or k8s_delete_kubernetes_node_pool. 'Smart identifier resolution' explains identifier formats, not usage context, so the description leaves the when-to-use decision entirely to the agent.

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