iaas_enumerate_private_images_vcf

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the description's main contribution is the 'enabled regions' scoping detail. It does not disclose that a POST-based enumeration typically kicks off an asynchronous job or what the caller must do afterward, which is meaningful context the annotations don't carry.

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?

Two short lines with the purpose front-loaded and no filler. The second line is the raw endpoint path, which largely duplicates the annotation title, so it earns little of its space.

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 mutation-flagged, open-world POST with no output schema, the description should say what the call returns (likely a request tracker/id) and that results are retrieved separately. That guidance is absent, leaving a gap an agent would hit at invocation time.

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 both the account id and apiVersion are already documented in the schema. The description only restates that an account id is required; it adds no format, sourcing guidance (where to obtain the VCF account id), or versioning advice beyond the schema's own pointer.

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 private images) with a clear provider scope ('VCF account' and 'enabled regions'), which distinguishes it from the AWS/Azure/GCP/vSphere/VMC variants. It does not explicitly name those siblings, so differentiation relies on the provider token in the name rather than prose.

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?

Usage is only implied: call this when you want private images for a VCF cloud account. Nothing says when to use the generic iaas_enumerate_private_images instead, what prerequisites exist (e.g., a completed account onboarding/region enumeration), or whether this must be followed by a request-tracker poll.

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