iaas_enumerate_private_images_azure

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the "enabled regions" scoping and the REST path, but leaves a key behavioral question unanswered: whether this kicks off an asynchronous enumeration job that must be polled, which matters for a non-idempotent POST with external calls. No contradiction, but the useful extra context is thin.

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, front-loaded with the operation and scope before the endpoint path. The trailing POST path is mildly redundant with the annotation title but does anchor the call for an agent working from the API surface.

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, so the description must carry the burden of explaining what comes back — and it does not say whether the call returns a request tracker/job id, a list of images, or an async status. For a non-idempotent provider-side enumeration with only two params, that omission is the main 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%, with both `id` (the Azure cloud account id, path) and `apiVersion` documented inline. The description only restates that the id identifies the Azure account and adds no format, source, or lookup guidance, so the schema is doing the semantic work.

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), resource (private images), and scope (enabled regions of a specified Azure account), which clearly separates it from the AWS/GCP/VMC/vSphere/VCF enumeration siblings. It does not, however, contrast itself with the generic iaas_enumerate_private_images or with iaas_get_images, so the differentiator is only implied by the provider 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?

The provider-specific scope is implied by "Azure account," which is enough for an agent to pick this over the AWS/GCP variants. But there is no explicit when-to-use guidance, no mention of whether results must be retrieved separately (e.g. via iaas_get_region_enumeration_result or an image listing tool), and no prerequisites beyond the account id.

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