timeweb_delete_k8s_cluster

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

The word 'permanently' discloses the irreversible nature of the deletion, which is valuable for a destructive operation. However, with no annotations present, the description does not address associated resources, permissions, or return values, leaving significant behavioral gaps.

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 a single sentence with no extraneous words, immediately conveying the core action and its permanence. It is optimally concise.

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?

The description is too sparse for a destructive tool. It does not explain what happens to the cluster's associated resources, whether deletion is immediate, or what kind of response to expect. The format parameter suggests output options but is not referenced, and the lack of an output schema or annotations makes the description insufficiently 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 fully describes both parameters (format and cluster_id) with clear descriptions and enumeration for format. The description adds no parameter-level details, so a baseline score of 3 applies given the high schema coverage.

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 states the action ('Delete') and the target resource ('a Kubernetes cluster') with an added qualifier 'permanently', making the tool's purpose unmistakable and distinguishing it from sibling deletion tools like delete_server or delete_database.

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?

No guidance is provided about when to use this tool, what prerequisites must be met, or alternative tools. The description only states the action without context about cluster state or confirmation requirements.

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