vcluster_delete

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 discloses the irreversible nature, permanent removal of resources, and default behavior for namespace and kubeconfig_path. However, the phrase 'optionally its namespace' is ambiguous—it doesn't clarify exactly when the namespace gets deleted, since there is no explicit boolean parameter controlling this.

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 well-structured, starting with a clear summary, then detailed parameter explanations, and a return specification. Every sentence adds useful information without unnecessary fluff, making it concise yet comprehensive.

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?

Given that an output schema exists and there are only 3 parameters, the description covers the key aspects: operation, irreversibility, parameter defaults, and return type. It lacks explicit details about the namespace deletion trigger and whether the operation is synchronous, but these are minor omissions.

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 0%, so the description is essential and compensates well. It explains each parameter's purpose, including defaults (namespace defaults to the vcluster name, kubeconfig_path defaults to the environment kubeconfig). The only minor gap is the unclear relationship between the namespace parameter and whether deletion of the namespace is conditional.

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 clearly states 'Delete a vcluster' and expands on the operation, specifying it deletes the vcluster and optionally its namespace. This distinguishes it from sibling tools like vcluster_pause, vcluster_resume, and vcluster_list, which serve different lifecycle operations.

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 clearly communicates that this tool is for permanent deletion, with an explicit warning that the action is irreversible. It does not name alternatives (e.g., vcluster_pause) for non-destructive suspension, but the context makes it obvious when to use this tool versus others.

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