iaas_get_fabric_networks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only the endpoint path, which duplicates the title and contributes no behavioral context such as pagination defaults or return shape.

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?

It is short, but also redundant: 'Get fabric networks', 'Get all fabric networks', and the endpoint path all restate the same fact rather than front-loading useful constraints. Nothing is wasted in length, but nothing is earned either.

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?

With no output schema and six well-documented parameters, the description is just barely adequate: annotations carry safety, schema carries parameters, but the description gives no guidance on filtering or pagination behavior for a list endpoint.

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 coverage is 100% with all six parameters (top, skip, count, filter, select, apiVersion) documented in the schema. The description adds no meaning beyond what the schema already provides, so the 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 ('Get all fabric networks') so the agent knows this is a list operation on fabric networks, distinguishable from the singular iaas_get_fabric_network. It does not, however, differentiate itself from related siblings like iaas_get_vsphere_fabric_networks or iaas_get_networks.

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 when-to-use guidance, no mention of prerequisites, and no named alternative. The agent must infer from the name alone that this lists all fabric networks rather than a filtered subset.

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