iaas_get_fabric_vsphere_storage_policy

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond restating the operation and pasting the HTTP path — no information about error behavior when the ID doesn't exist, or what the returned policy contains.

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, but the first two lines are near-verbatim duplicates ("Get fabric vSphere storage policy" repeated), and the raw HTTP path adds little for an agent. Front-loaded but with wasted repetition.

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 simple read-by-ID tool whose annotations cover safety, the essentials are present. However, with no output schema, a phrase describing what a fabric vSphere storage policy record contains (or that it returns 404 for unknown IDs) would have closed the remaining gap.

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 all three parameters (id, select, apiVersion) are documented in the schema itself. The description only mentions "a given id" and adds no meaning about the select projection or API versioning semantics, so 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?

The description names a specific verb and resource ("Get fabric vSphere storage policy") and adds "with a given id", which distinguishes this single-item fetch from the plural list sibling iaas_get_fabric_vsphere_storage_policies. The purpose is unambiguous, though the sibling routing is only implied by the singular form rather than stated.

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 alternatives such as iaas_get_fabric_vsphere_storage_policies, nor on prerequisites like needing a valid fabric policy ID from a prior list call. Usage must be inferred entirely from the name.

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