esxi_list_networks

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

No annotations are provided, and the description only says 'List all networks and port groups on ESXi'. It does not disclose whether the operation is read-only, what permissions are needed, or any side effects. Even for a list operation, the minimal disclosure leaves the agent guessing about safety and behavior.

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 single, concise sentence that conveys the core function with no unnecessary words. It is appropriately sized for a simple list tool and is easy 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?

For a simple one-parameter list operation, the description is adequate but sparse. It does not explain return structure or any caveats, and with no output schema or annotations, the agent must infer behavior. It covers the basics but leaves gaps for a complete understanding.

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 already fully describes the only parameter (device_id) as 'ESXi host device ID', and the description adds no additional semantics about how the parameter is used. With 100% schema coverage, the baseline is 3, and the description does not elevate it.

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 lists all networks and port groups on ESXi, using a specific verb and resource. It distinguishes itself from sibling tools like esxi_list_vms and esxi_list_datastores by explicitly naming the network-related scope.

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 when the agent needs to see networks/port groups on an ESXi host, but it does not explicitly state when to use it over alternatives or mention any prerequisites or exclusions. The context from siblings helps, but no direct guidance is provided.

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