esxi_shell

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds meaningful beyond-annotation context: administrator gating, the separate SSH requirement, dual approval via management-link and protection-impact flags, no automatic retry, and that full dependency inference is impossible. These are genuine operational traits. It stops short of what gets destroyed or a recovery path.

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?

It is a single dense sentence with the gating constraints front-loaded and no filler. It is compact and information-rich, though the density and mixed metaphors ('management entry', 'link/protection') make it slightly hard to parse.

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?

An output schema exists, so return values need not be described, and the description covers the critical safety gating for a hazardous execution tool. It is still incomplete: no guidance on the dry_run default or on how to satisfy the dual-approval and acknowledgement parameters an agent must set to proceed.

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 0% across 8 parameters, so the description must carry the full load; it only obliquely maps to allow_disruption/allow_protected_impact via 'dual allowance.' dry_run, timeout, expected_host, max_output_bytes, and acknowledged_vm_ids are never explained, leaving their semantics undocumented anywhere.

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 calls itself the explicit host-wide ESXi shell entry point, which implies arbitrary shell command execution on the host, but the framing ('shell management entry') is abstract rather than a crisp verb+resource. It does not clearly state 'execute a command on the ESXi host' nor contrast itself with close siblings like esxi_esxcli or esxi_guest_process. Purpose is inferable but not sharply defined.

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?

It lists real prerequisites: administrator-only access, SSH enabled as an independent switch, and dual allowance of management link and protection impact. However it gives no explicit when-to-use/when-not-to-use against alternatives such as esxi_esxcli or esxi_api_invoke, so routing among the many shell/API siblings is left to inference.

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