iaas_enumerate_private_images_vsphere

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the safety profile is largely covered. The description adds nothing beyond the endpoint: it does not say that enumeration is a triggered job, whether it returns a request tracker, how long it takes, or what permissions the account needs — all of which are the non-obvious behaviors for this call.

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 purpose is front-loaded in a single clean sentence, which is good. But the trailing raw path 'POST /iaas/api/cloud-accounts-vsphere/{id}/private-image-enumeration' is verbatim duplication of the annotation title and earns no place in the description.

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?

There is no output schema, the tool is non-idempotent and open-world, and it likely kicks off a background enumeration whose results surface elsewhere (e.g., via iaas_get_images or fabric image tools). None of that is conveyed, so an agent cannot tell what happens after invoking it or how to retrieve results.

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 both the path id and the apiVersion already documented in the schema. The description's phrase 'specified vSphere account' loosely maps to id, but adds no format, constraint, or enumeration semantics beyond what the schema 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 ('Enumerate all private images') scoped to 'enabled regions of the specified vSphere account,' which is precise enough for an agent to understand the operation. However, it never distinguishes itself from the many sibling enumerators (iaas_enumerate_private_images_aws/azure/gcp/vmc/vcf, iaas_enumerate_private_images), leaving the provider split implied only by the tool name.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. With roughly a dozen sibling enumerate tools in scope, an explicit statement such as 'use for vSphere accounts only; other providers have separate tools' would be the single highest-value addition, and it is absent.

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