vmware_list_hosts

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context by specifying the output structure (JSON and markdown formats) and the fields included, such as host metadata and usage metrics. No contradictions with annotations.

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 front-loaded with the main purpose and a bullet-like list of fields. It is reasonably concise, though the inline representation of JSON and markdown could be a bit more streamlined. It still effectively communicates the essential information without excess.

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 that the tool has a read-only, idempotent nature with annotations and an output schema, the description provides sufficient completeness. It covers what data is returned, the output formats, and hints at pagination through the parameters. No missing critical information for an agent to use the tool correctly.

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 the schema already documents all three parameters (limit, offset, response_format). The description adds minimal extra meaning beyond restating the response_format options, which are already described in the schema. 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 clearly states the tool's function: 'Lists the ESXi hosts' and specifies the included fields (state, version, model, CPU/RAM load, VM count). It distinguishes itself from sibling tools like vmware_get_host (single host) and vmware_list_vms (virtual machines) by its scope and output details.

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 provides no explicit guidance on when to use this tool versus alternatives. While the context of listing all hosts is implied, there is no mention of prerequisites, limitations, or when not to use it (e.g., for a single host, use vmware_get_host instead).

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