iaas_create_data_collector

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the mutation/safety profile is covered. The description adds the on-prem availability caveat, which is real added context, but says nothing about permissions required, side effects of creation, or what the resulting resource looks like.

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?

Short and front-loaded, with the availability caveat placed before the raw endpoint. The first line duplicates the title and the second line restates it, which is mild waste but not harmful.

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?

With no output schema and full param coverage, the description only needs to cover behavior and scope. It does name the endpoint and the on-prem limitation, but leaves the biggest question (what payload is required to create a collector, given the schema exposes only apiVersion) unaddressed.

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% for the single apiVersion parameter, so the baseline is 3. The description adds no meaning beyond the schema — notably it never addresses that a POST to /data-collectors normally requires a body, which the schema does not expose.

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+resource ('Create a new Data Collector'), which cleanly distinguishes it from sibling tools like iaas_get_data_collectors and iaas_delete_data_collector. It does not, however, describe what a data collector is or how it relates to the endpoints around it.

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 not available in VMware Aria Automation (on-prem) release' is a genuine usage constraint, but there is no guidance on when an agent should create one, what prerequisites exist, or which sibling to use instead for related operations.

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