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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them: it discloses that nodes are drained and terminated at the cloud provider, that local data is destroyed, the irreversibility caveat, and the last-pool constraint. This is exactly the behavioral context an agent needs before a destructive call.

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 tight sentences with the destructive nature front-loaded ('PERMANENTLY'), followed by consequences and the sole constraint. Every sentence earns its place with no filler.

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 delete tool with no output schema, the description covers consequences, reversibility, and the key restriction completely. Nothing an agent needs to invoke it safely 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 pool_name, cluster_id, and cluster_name are already documented in the schema. The description does not add syntax, formatting, or selection guidance beyond what the schema provides, so the baseline of 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 (PERMANENTLY delete), a precise resource (a node pool from a managed Kubernetes cluster), and the scope of the operation. An agent can immediately distinguish it from update_managed_node_pool, list_managed_node_pools, or add_managed_node_pool without opening any 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?

Explicitly states the key guardrail ('the last remaining node pool cannot be deleted') and names the sibling to use for the opposite action (add_managed_node_pool). It does not, however, contrast against related delete tools like delete_node_group or delete_cluster, leaving some sibling routing to inference.

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