list_virtual_centers

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

No annotations are provided, so the description carries the burden of disclosing behavior. The verb 'List' and phrase 'configured in the environment' reasonably convey a read-only, non-mutating operation. It does not mention authentication prerequisites, pagination, or side effects, but the absence of both parameters and mutation suggests minimal behavioral risk.

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 a single, front-loaded sentence with no wasted words. It expresses the action, resource, and scope without artifact or ambiguity.

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?

Given zero parameters and the presence of an output schema, the description is complete enough for an agent to invoke the tool correctly. It clearly identifies the resource being listed and the environment scope, and there is no separate return-format explanation needed because the output schema exists.

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?

The input schema has zero parameters, so there are no parameter semantics to add. The baseline for no-parameter tools applies, and the description appropriately focuses on the tool's scope rather than pretending to document parameters.

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 names a specific verb and resource: 'List all vCenter Servers configured in the Horizon environment'. This clearly distinguishes it from sibling list tools such as list_connection_servers and list_gateways.

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: call this tool whenever you need the full set of vCenter Servers in the environment. It does not explicitly mention alternatives or state when not to use it, but for a zero-parameter list-only operation the context is fairly self-evident.

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