esxi_inventory

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the set of entity types returned; it says nothing about result size, default behavior of the limit parameter, or whether the inventory is snapshot/current-state based, so it provides modest extra context.

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?

A single front-loaded sentence that names the action and the payload entity types with no filler. It is well sized for a simple listing tool, though it spends its words on enumerating types rather than on the ambiguities that matter.

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, but with two undocumented parameters and roughly 65 sibling tools the description leaves the key questions unanswered: how resource_type selects entities and how this differs from the specialized list tools. It is not complete enough for an agent to invoke confidently without inspecting the schema.

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% for both parameters, so the description must carry the burden. It loosely hints at the domain of resource_type by naming entity kinds, but never explains that resource_type takes SDK type strings (default 'vim.ManagedEntity') or what limit=200 governs. The compensation is partial at best.

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 (列出) and resource (SDK 管理实体) and enumerates the entity kinds it covers (VM、HostSystem、Datastore、Network、Folder、ResourcePool), so the intent is unambiguous. However, it offers no differentiation from the many overlapping siblings such as esxi_list_vms, esxi_list_datastores, and esxi_list_networks that appear to retrieve much of the same data.

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?

There is no statement of when to use this generic inventory tool versus the specialized list tools in the sibling set, nor any prerequisite, exclusion, or scope condition. An agent facing esxi_list_vms/esxi_list_datastores/esxi_host_summary cannot infer from this text which one to pick.

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