azure_find_cheapest_region

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does reveal that the result is a top-N, price-sorted list, which signals a read-only lookup, but it does not disclose pricing basis, units, availability caveats, or the concrete response shape beyond the sorting.

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 two short sentences with no redundant wording. The core purpose is front-loaded and the output behavior is stated concisely in the second sentence.

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 tool has five parameters and no output schema, yet the description covers only the high-level purpose and top-N ordering. The schema supplies defaults and enums, which helps minimally, but the description leaves out output-format expectations and does not clarify why it should be selected over the closely related pricing siblings.

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 0%, so the description must compensate for parameter meaning. It only maps 'VM SKU' to armSkuName and 'top N' to topN; it adds no meaning for priceType, currencyCode, or response_format. The schema's defaults and enums provide some structure, but the description does not explain their intended use.

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 states a specific action — finding the cheapest Azure regions — scoped to a given VM SKU, and notes that it returns top N results sorted by price. This is clear and distinct in substance, but it does not explicitly differentiate from siblings like azure_search_prices or azure_compare_vm_prices.

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 'for a given VM SKU' implies the intended use case: select this tool when you need the cheapest regions for one SKU. However, there is no explicit guidance on when not to use it or which sibling tool to prefer for related scenarios such as comparing multiple SKUs or pricing models.

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