delete_cluster_pool

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

Beyond the destructiveHint annotation, the description adds that worker nodes are drained and destroyed, and that the operation is rejected if it would leave zero pools. This provides meaningful behavioral context without contradicting annotations.

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?

Three sentences with no wasted words. The most critical information (action, destructiveness, constraints, parameter sources) is front-loaded and efficient.

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?

No output schema, and the description does not mention what the tool returns on success or failure. For a destructive action, agents would benefit from knowing the expected response (e.g., a confirmation object). Otherwise, the description covers inputs and constraints adequately.

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 coverage is 100%, so baseline is 3. The description adds value by explaining how to obtain service_id (from list_services) and pool (from list_cluster_pools), and for confirm clarifies the refusal behavior when not true. This is helpful but not extensive.

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 uses a specific verb ('Remove') and resource ('worker node pool from a managed Kubernetes cluster'), clearly distinguishing it from sibling tools like add_cluster_pool, update_cluster_pool, and rename_cluster_pool.

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?

Provides clear context: requires scope services:write, states the constraint that the last pool cannot be removed, and mandates user approval via confirm:true. However, it does not explicitly compare to alternatives (e.g., update_cluster_pool) but the naming is sufficiently distinct.

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