iaas_get_fabric_vsphere_datastore

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds nothing beyond restating the endpoint — no mention of permission requirements, error behavior for missing ids, or whether the record is scoped (e.g., by org/project).

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 and front-loaded, but the three lines are redundant: the first and second sentences say the same thing, and the third is a raw path that adds little. Some tightening would help.

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 tool with no output schema and a rich sibling ecosystem, the description should indicate what a datastore record contains or how it differs from the list endpoint. As written it is a bare minimum restatement, leaving the agent to infer the return shape entirely.

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%, so all three parameters (id, select, apiVersion) are already documented. The description's 'with a given id' maps to the id param but adds no syntax or formatting guidance; baseline 3 applies when the schema does the heavy lifting.

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 the verb and resource ('Get fabric vSphere datastore') and 'with a given id' hints at single-resource retrieval, which does separate it from the list sibling iaas_get_fabric_vsphere_datastores. However, the second sentence is essentially a restatement of the first plus the raw HTTP path, not a substantive explanation of what is retrieved.

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 vs the list variant iaas_get_fabric_vsphere_datastores, no prerequisites, and no exclusions. The 'given id' phrasing is the only implicit selection hint.

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