list_locationsRetrieve the Azure regions available to a subscription. Use to check location allowlists or plan resource deployment targets.
List the regions available to a subscription.
| Name | Required | Description | Default |
|---|---|---|---|
| subscription | No | Subscription id (defaults to AZURE_SUBSCRIPTION_ID) |
Changes observed during successful MCP inspections.
v0.2.2Input schema / additionalPropertiesRemoved value: -falsev0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds little beyond that—it doesn't mention pagination, output format, or the significance of 'available' regions (e.g., availability for deployment).
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?
A single, concise sentence that is front-loaded with the action and resource. No extraneous words.
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 simple list tool with full schema coverage and annotations, the description is adequate but minimal. It lacks any mention of the return structure or sorting, and does not provide usage context. Output schema is absent, but for a list operation the return format could be inferred.
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 single parameter (subscription) is fully documented in the schema, including the default behavior. The description adds no parameter details, so a baseline 3 is appropriate.
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 (list) and resource (locations/regions) scoped to a subscription. It is distinguishable from siblings like list_resources and list_resource_groups, though it slightly uses 'locations' and 'regions' interchangeably without clarifying this.
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 guidance on when to use this tool versus alternatives like list_resources or list_subscriptions. The context of needing a subscription's regions is implied but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.