iaas_delete_data_collector

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the agent knows this is an irreversible write. The description adds only the on-prem availability caveat and the raw endpoint path; it does not say what dependent objects are affected, whether the data collector must be stopped/unregistered first, or what the response is.

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?

Three short lines, front-loaded with the action statement and followed by the availability caveat. The first two lines restate each other ('Delete Data Collector' / 'Delete Data Collector with a given id'), a minor redundancy that keeps it off a 5.

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 two-parameter delete with full schema coverage, rich annotations and no output schema, the description supplies the one non-obvious fact an agent needs: this API is not present on the on-prem release. Nothing else is strictly required, though a note on preconditions would round it out.

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 both parameters (id and apiVersion) are already documented in the schema. The description adds no format hints, ID-source guidance, or apiVersion behavior, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete Data Collector with a given id') and includes the underlying endpoint, so the operation is unambiguous. It does not explicitly contrast with siblings such as iaas_get_data_collector or iaas_create_data_collector, but the verb makes the distinction obvious.

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 note that data collector endpoints are unavailable in the VMware Aria Automation on-prem release is a genuine when-not-to-use constraint that most sibling deletes lack. It stops short of naming alternatives or prerequisites (e.g., what must be true before deletion), so it isn't a full usage rule set.

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