iaas_get_vsphere_fabric_networks

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — no note on pagination defaults, result volume, or permission requirements for reading fabric networks.

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 first two sentences say exactly the same thing ('Get vSphere fabric networks' / 'Get all vSphere fabric networks'), which is pure redundancy. Only the endpoint path carries marginal extra information.

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 paged list tool with complete schema coverage and full annotations, the description is minimally sufficient. It omits any hint about what a fabric network record contains or how large the collection typically is, but there is no output schema requiring explanation.

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 100%, so all six query parameters (top, skip, count, filter, select, apiVersion) are already documented in the schema. The description adds no interpretation of them, which is acceptable given the full coverage — baseline 3.

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 verb ('Get') and resource ('vSphere fabric networks') are specific and unambiguous, and the REST endpoint path confirms it is a collection GET. It does not, however, distinguish this from sibling iaas_get_fabric_networks (all fabrics) or iaas_get_vsphere_fabric_network (single item).

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 versus iaas_get_fabric_networks or iaas_get_vsphere_fabric_network, despite those siblings being easy to confuse with this one. The only guidance is the implicit 'all' in the second sentence.

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