azure_list_active_locations

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

With no annotations, the description must disclose behavior. It states it checks resource groups, VMs, storage accounts, and AKS clusters, and mentions scan modes. However, it does not explicitly state that the tool is read-only or describe output behavior beyond format options in the schema.

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?

The description is concise with two sentences. The main purpose is front-loaded. The second sentence adds context, but the phrase 'Quick scan' is somewhat redundant. No unnecessary details.

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?

The description explains what the tool does but lacks details about output format (though schema provides options). For a simple list tool, it is mostly complete, but could benefit from specifying that the output lists region names or statuses.

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 parameters are already documented. The description adds context about what resources are checked but does not elaborate on parameter usage beyond the schema. Baseline score of 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?

The description clearly states the tool's purpose: 'Discover which Azure locations have resources deployed.' It specifies the verb (discover/scan) and resource (Azure locations), and distinguishes from sibling tools like azure_scan_all_locations by focusing on active regions for quick identification.

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 phrase 'Quick scan to identify active regions before deep scanning' provides clear usage context, implying this tool is a preliminary step. However, it does not explicitly mention when not to use it or list alternative tools.

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