iaas_get_fabric_vsphere_datastores

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds nothing further—no note on pagination behavior, result volume, or what the endpoint returns—beyond restating the GET path, which also appears in the annotation title.

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 two of the three lines say essentially the same thing ('Get fabric vSphere datastores' / 'Get all fabric vSphere datastores') and the third is the raw endpoint path. There is redundancy rather than front-loaded added value.

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 annotations carrying the safety profile, the minimal description is technically sufficient to call the tool. However, it gives no context on the vSphere fabric domain or how these datastores relate to storage profiles and datastore-facing siblings, leaving the agent to infer scope.

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 top, skip, count, filter, select, and apiVersion are already fully documented in the schema. The description adds no syntax hints or defaults beyond that, which is the expected baseline when the schema does the work.

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 states a specific verb and resource ('Get all fabric vSphere datastores'), making the collection being returned unambiguous. The plural 'datastores' implicitly distinguishes it from the sibling iaas_get_fabric_vsphere_datastore (singular), but no explicit differentiation is given.

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 singular sibling iaas_get_fabric_vsphere_datastore or the many other get-list endpoints, and no prerequisites or exclusions are mentioned. The agent must infer usage from the name alone.

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