iaas_get_data_collectors

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context by warning that data collector endpoints are unavailable in the on-prem VMware Aria Automation release.

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 short and front-loaded, with the availability caveat placed prominently. It has minor redundancy between the heading 'Get Data Collectors' and the sentence 'Get all Data Collectors,' plus the raw endpoint path restates the annotation title.

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 simple read-only list endpoint with full parameter schema coverage and rich annotations, the description is largely complete. The main omission is that it does not explain response shape or whether pagination applies, though no output schema exists and the tool has no required parameters.

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 are fully documented in the schema. The description adds no additional parameter semantics beyond stating that it retrieves all data collectors, so the baseline score 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 states a specific verb and resource: 'Get all Data Collectors.' The word 'all' distinguishes this list operation from the sibling singular tool iaas_get_data_collector, and the on-prem availability caveat adds useful scope.

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?

It provides a clear usage context ('Get all') and a when-not caveat for VMware Aria Automation on-prem. However, it does not explicitly route the agent between this tool and the singular iaas_get_data_collector or other sibling list endpoints.

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