delete_drs_rule

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

Goes well beyond the destructiveHint annotation by explaining the confirm-gated preview/delete flow, that both preview and result record the full rule definition for audit recovery, that the operation is audited, and that errors return a dict with 'error' and 'hint'. This gives the agent a clear model of side effects and failure behavior.

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?

Well-structured and dense: the WRITE marker and purpose are first, then the key exclusion, then behavioral/audit context, then return shape. Every sentence earns its place and nothing is redundant.

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 confirm-gated tool with no output schema and no enum constraints, this description covers the essential operational context: what it deletes, what it refuses, the preview/delete contract, auditability, and error shape. An agent has enough to invoke it safely and interpret the response.

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 coverage is 100% and the schema already provides strong descriptions for confirm, cluster, rule_name, and target. The description adds useful behavioral context about the preview/result flow, but it does not substantially add parameter-level meaning beyond what the schema already says.

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?

Starts with a specific verb and resource: 'Delete a VM-VM DRS rule'. It also narrows the scope to VM-VM rules only and clearly distinguishes this from sibling tools like create_drs_rule, set_drs_rule_enabled, and list_drs_rules.

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 when not to use the tool: non-VM-VM rules are refused and should be managed in the vSphere UI. It also reinforces the confirm-gated workflow by warning that the caller should not blindly set confirm=true before a preview has been seen.

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