iaas_get_vsphere_fabric_network

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is fully covered by structured data. The description adds nothing beyond that — no return shape, no error behavior for an unknown id, no cross-tenant/openWorld caveat — so it does not earn credit on top of annotations.

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?

Three lines state the same thing twice — 'Get vSphere fabric network' is immediately restated as 'Get vSphere fabric network with a given id' — and the third line's HTTP path duplicates the annotation title. Front-loaded purpose is fine, but roughly half the text is redundant.

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 read-only single-resource fetch with a fully documented 3-parameter schema, the essentials are technically present. However, with no output schema, the description should hint at the returned fabric-network object, and it gives no hint about the neighboring endpoints an agent could confuse this with.

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% for all three parameters (id, select, apiVersion), so the schema carries parameter documentation. The phrase 'with a given id' weakly echoes the required path parameter and adds no new semantics for select or apiVersion; baseline 3 applies.

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?

States a specific verb and resource: retrieves a single vSphere fabric network by id. It is clear what the tool returns, but it never distinguishes itself from near-identical siblings such as iaas_get_fabric_network, iaas_get_vsphere_fabric_networks (plural list), or iaas_updatevsphere_fabric_network, which an agent must disambiguate from the name alone.

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 guidance on when to use this tool versus the plural list endpoint or the generic fabric-network endpoint. 'with a given id' implies you need an id, but nothing states where to obtain one or when the collection variant is the better call.

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