iaas_enumerate_azure_regions_async

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the agent knows this is a non-idempotent outward-facing POST rather than a simple read. The description adds the endpoint path but does not explain the async request/tracker behavior, credential handling, or that credentials in the body are sensitive — the one thing an agent most needs beyond the hints.

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 plus the raw POST path — front-loaded and free of filler. The endpoint string adds little for an agent but costs almost nothing.

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 non-idempotent, async enumeration tool with a nested credential-bearing body and no output schema, the description omits the critical fact that this is asynchronous and how results are retrieved. An agent could call it correctly in shape but be stranded on what to do with 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%, and the nested body properties already spell out the tenantId/cloudAccountId and subscriptionId/cloudAccountId either-or patterns. The description contributes nothing beyond the schema, 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 (get available regions) scoped to Azure cloud accounts, which implicitly separates it from the AWS/GCP/vSphere enumeration siblings. It stops short of flagging the async nature implied by the tool name, so an agent cannot tell from the description alone that this kicks off a request rather than returning regions directly.

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 pick this over the generic iaas_enumerate_regions_async, the per-provider siblings, or iaas_get_region_enumeration_result. No prerequisite or follow-up step is mentioned, so the agent must infer the whole polling workflow from sibling names.

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