Find Azure VM sizes

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context: prices are monthly USD list prices, and burstable/confidential families are silently excluded unless explicitly requested — a non-obvious filtering trait that affects result interpretation.

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 sentences, both load-bearing: the first covers purpose and output units, the second covers the default exclusion rule. The most decision-relevant information (what it finds and at what price basis) is front-loaded with zero filler.

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?

With 10 all-optional parameters, no required inputs, and no output schema, the description supplies what the schema cannot: the default filtering behavior and price basis. It does not describe result ordering limits or tie-breaking beyond what sort/ max_results already say, but nothing essential to calling it correctly is missing.

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%, so every parameter including the enum semantics (ai vs gpu, sort=price vs fit, region default) is already documented in the schema. The description reinforces that vCPU, memory and workload drive the match, but adds no syntax or format detail beyond it, 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 ("Find the cheapest Azure VM sizes") plus the qualifying dimensions (vCPU, memory, workload) and the delivered artifact (monthly USD list prices). It is clearly distinguishable from get_vm_size (singular detail) and estimate_vm_cost (costing), though it never names a sibling explicitly.

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 sentence "Burstable (B-series) and confidential sizes are only included when that workload is requested" is a genuine usage rule about default behavior. However, there is no explicit when/when-not guidance and no routing to the sibling tools, so the agent must infer that this is the discovery step before estimate_vm_cost.

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