iaas_get_data_collector

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a meaningful availability constraint noting the endpoint is unavailable in on-prem releases, but it does not describe response behavior or errors.

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, but it redundantly repeats 'Get Data Collector' in the first two sentences and then restates the REST endpoint. The availability caveat is useful, but the repetition reduces efficiency.

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 get-by-id retrieval with full schema coverage and read-only annotations, the description is largely complete. The main omission is a brief statement of what is returned, though the tool is simple enough that this is a minor gap.

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%, and the schema already documents both id and apiVersion. The description only repeats that an id is required and adds no format, example, or apiVersion guidance beyond the schema.

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: get a Data Collector by a given id. This distinguishes it from the plural list tool iaas_get_data_collectors, though the description does not explicitly name sibling tools.

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?

Usage is implied by the required id parameter, but the description does not explicitly say when to use this versus iaas_get_data_collectors or other alternatives. It does add a useful availability caveat for VMware Aria Automation on-prem.

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