ibmcloud_ks_cluster_delete

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention that deletion is destructive, irreversible, or potentially cascading, and it does not warn about the need for confirmation or force flag implications. This is a significant gap for a mutating operation.

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 extremely short and front-loaded, avoiding verbosity. However, it is under-specified, lacking any additional context or structure that could aid an agent. It is not overly long but also not helpfully concise; it simply states the obvious.

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 operation with no annotations and no output schema, the description should provide more context about consequences, reversibility, or caveats. The schema covers parameter syntax, but the description fails to make the tool safe and complete for an agent to invoke properly.

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 the input schema already documents both parameters (cluster name/ID and force). The description adds no extra semantic value beyond what the schema provides, but it does not need to since the schema is sufficient. Baseline of 3 is appropriate.

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 ('Delete') and a clear resource ('Kubernetes cluster'), distinguishing it from sibling tools like create, config, or list. It unambiguously states the tool's core function with minimal ambiguity.

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 on when to use this tool or when to prefer an alternative. There is no mention of prerequisites, exclusions, or comparisons to other cluster-related commands. The description simply states the action without any usage context.

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