k8s_delete_kubernetes_node_pool

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

No annotations are provided, so the description carries the full burden. It does disclose two behavioral details: smart identifier resolution and a returned deletion status message. However, it fails to mention that deleting a node pool may also delete all associated nodes or that the operation is likely irreversible, which is critical for a destructive action.

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 short and front-loaded: a one-sentence purpose, one-sentence identifier note, an A args list, and a Returns section. Every element adds necessary value and there is no fluff or repetition.

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?

While the description provides a clear purpose, parameter definitions, and return type, it leaves out consequential side effects—like whether node deletion is recursive—and any safety or prerequisite information for a destructive operation. The lack of annotations makes this a noticeable gap, though the core details are covered.

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, so the description compensates by defining each parameter: 'The cluster label or ID' and 'The node pool label or ID to delete'. It also adds the 'smart identifier resolution' note that clarifies label vs UUID semantics beyond the bare schema.

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 opening phrase 'Delete a node pool from a Kubernetes cluster' uses a specific verb and resource, immediately distinguishing it from sibling tools like k8s_delete_kubernetes_node or k8s_delete_kubernetes_cluster. The name itself also carries the action, but the description reinforces the scope ('from a Kubernetes cluster').

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 does not provide when-to-use guidance or mention alternative tools. It explains 'smart identifier resolution' but never states when this tool should be preferred over related actions or what prerequisites exist, leaving the agent without direction on tool selection.

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