vsphere_list_networks

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

The description only adds 'using the vSphere Automation REST API', which is implementation detail and not behavioral. Annotations already fully disclose readOnlyHint, idempotentHint, and destructiveHint. No additional behavioral traits (e.g., permission requirements, pagination, or scope of 'visible') are disclosed.

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, short sentence that conveys the essential purpose without any unnecessary words. It is front-loaded and efficient.

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 tool with no parameters and a provided output schema (indicated by context), the description covers the core function. However, it lacks detail on what 'visible' means or how the network list is returned, which could be clarified given the complexity of vSphere.

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 input schema has zero parameters, so there is no need for parameter description. According to the guidelines, baseline is 4 for no parameters. The description does not add any parameter info, but none is needed.

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 verb 'List' and the resource 'visible networks', directly corresponding to the tool name. It unambiguously identifies the tool's function, distinguishing it from sibling tools like vsphere_list_vms or vsphere_list_hosts.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, context for use, or when not to use it. The usage context is only implied by the tool name and siblings.

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