vsphere_list_hosts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, establishing a safe read operation. The description adds context that it returns hardware, version, and live CPU/memory utilisation, and that pagination is available via limit/offset. No contradictions.

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 concise summary followed by a compact parameter list, front-loaded with the action. No wasted sentences.

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?

The tool has six optional parameters all described, and an output schema is present, so return values are already defined. The description covers the essential behavior and parameter semantics, making it complete for a list operation.

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 0%, but the description fully explains each parameter: name supports substring/glob, connection_state has enumerated values, limit/offset define pagination, and cluster/datacenter are filters. This provides crucial semantics absent from 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?

The description uses a specific verb ('List') and resource ('ESXi hosts'), and specifies the included data (hardware, version, live CPU/memory utilisation), clearly distinguishing it from sibling tools like vsphere_get_host which retrieves a single host.

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 description indicates it's for listing and filtering hosts with several optional filters, so the use case is clear. However, it does not explicitly differentiate from alternatives (e.g., vsphere_get_host for a single host) or state when not to use it.

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