vsphere_get_host

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds useful behavioral context by specifying accepted host identifier formats and the inclusion of attached VMs and datastores in the result, which goes beyond annotation coverage.

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 two short, front-loaded sentences for purpose plus a compact Args clarification. No filler or redundancy—every sentence earns its place.

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 single-parameter read-only tool with an output schema present, the description covers the core use case, identifier flexibility, and result scope. It does not discuss failure cases or performance, but given the annotations and output schema, this is acceptable. It slightly lacks explicit differentiation from vsphere_get_vm_summary_by_host, but the purpose is clear enough.

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 schema provides no description for the 'host' parameter (0% coverage), but the description's Args section fully compensates by explaining accepted formats: host name, managed object ID, hardware UUID, or inventory path. This adds meaning well beyond the bare 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 states a specific verb (get) and resource (one ESXi host), and specifies the output scope ('Full detail... including attached VMs and datastores'). This clearly distinguishes it from sibling tools like vsphere_list_hosts and vsphere_get_vm.

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 implies usage for retrieving detailed single-host data, contrasting with listing tools, but it does not explicitly name alternatives or state when not to use it. The context is clear but exclusion guidance is absent.

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