iaas_get_fabric_network_ip_ranges

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond restating the verb and the REST path – it does not mention pagination behavior despite top/skip parameters, nor whether an empty list is returned when no ranges exist.

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 same sentence is written twice verbatim before the endpoint path, which is pure waste. The endpoint line is arguably useful routing context, but the duplicated sentence should have been spent on scope or sibling differentiation instead.

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 list endpoint with full schema coverage and complete annotations, the description is minimally sufficient. It is still missing the two things an agent would want that structured fields don't supply: how the response is shaped/paged and how it differs from the near-identical sibling range endpoints.

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 every parameter (id, top, skip, apiVersion) is already documented in the schema. The description only reinforces that id identifies the fabric network; baseline 3 is appropriate when the schema carries the load.

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 names a specific verb and resource: retrieving IP ranges belonging to a fabric network identified by id. It is clear what the tool returns at a high level, but it never distinguishes itself from closely named siblings such as iaas_get_fabric_network_vsphere_ip_ranges, iaas_get_external_network_ip_ranges, or iaas_get_internal_network_ip_ranges.

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 choose this tool over the several other network-IP-range endpoints in the sibling list, nor any stated prerequisites (e.g. the fabric network must exist or be of a supported provider type). The only implied usage is the 'with a given id' scope, which the required parameter already conveys.

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