cluster_delete

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds '[WRITE]' and the precondition 'no hosts must remain', which is valuable behavioral context beyond annotations. However, it could mention implications like undeletable non-empty clusters.

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 concise: two sentences plus args list. The key information is front-loaded with '[WRITE]' and the precondition. No wasted words.

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 tool has an output schema (not shown) so return values are covered. With simple parameters and one required, the description is mostly complete. Minor gaps include error behavior or when cluster is not found.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: 'name' as the cluster to delete and 'target' as optional vCenter target. This adds meaning beyond the schema. More detail on name format could improve it.

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 the verb 'Delete' and resource 'cluster', with a critical precondition 'no hosts must remain'. This distinguishes it from sibling tools like cluster_create, cluster_configure, etc.

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 explains the parameters and precondition but does not explicitly state when to use this tool over alternatives or mention sequencing (e.g., remove hosts first). It provides clear context but lacks exclusions or alternative guidance.

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