iaas_update_fabric_network

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

Annotations already declare the mutation is not read-only, not destructive, not idempotent, and open-world. The description adds useful behavioral scope by stating that only tag updates are supported, preventing an agent from assuming it can update other fabric network fields.

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 short and front-loaded, but the first sentence 'Update fabric network.' is repeated verbatim, which wastes space without adding 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?

The mutation scope is clear and annotations cover the safety profile. Still, for an open-world PATCH operation with a nested body and no output schema, it does not explain whether unspecified fields are ignored, what success returns, or any permission requirements.

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 the inputs and nested tag body are already documented. The description reinforces that only tags are mutable but does not add syntax or semantics beyond what the schema provides.

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 gives a specific verb and resource — updating a fabric network — and narrows the operation to tag updates with the PATCH endpoint. It does not differentiate from the sibling `iaas_updatevsphere_fabric_network`, so an agent must infer which fabric network type applies.

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 phrase 'Only tag updates are supported' implies this is for metadata/tag changes and not broader network reconfiguration. However, it does not name alternatives or state when to use this instead of the vSphere-specific update sibling.

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