iaas_enumerate_private_images

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is partially covered. The description adds only the 'enabled regions' scope and does not disclose that this is an asynchronous, long-running enumeration that requires subsequent polling, which is the key behavioral fact for a POST-triggered job.

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?

One sentence that front-loads the verb and scope, with no wasted prose. The trailing raw API path is redundant with the annotation title but does not meaningfully bloat the text.

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?

With no output schema and an async operation behind a POST, the description should indicate that the call returns a request tracker to poll (siblings like iaas_get_request_tracker exist for this). That critical lifecycle information is absent, leaving the agent unable to interpret the response.

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%, with both 'id' and 'apiVersion' documented in the schema. The description's phrase 'specified cloud account' loosely maps to 'id' but adds no format or versioning detail beyond what the schema already gives, 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?

States a specific verb ('Enumerate') and resource ('private images') scoped to 'enabled regions of the specified cloud account', so the action is unambiguous. However, it does not differentiate itself from the many provider-specific siblings (iaas_enumerate_private_images_aws/azure/gcp/vmc/vsphere/vcf), so an agent must infer that this is the generic/cross-provider variant.

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 explicit guidance on when to use this versus the provider-specific enumerate_private_images_* siblings, nor on prerequisites such as the cloud account needing to exist or be enabled. Usage is only implied by the phrase 'for enabled regions'.

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