Azure VM size details

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds genuine behavioral context beyond that: it enumerates the pricing dimensions (Linux, Windows, reservations, savings plans) and the output ordering ('cheapest region first'), which an agent needs to interpret results.

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 dense sentence that front-loads what the tool returns and ends with the sort order. Every clause carries information, though the parenthetical pricing enumeration is heavy for one line.

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 no output schema, the description compensates by naming what is returned (specs, hourly USD prices by pricing model) and the ordering, which is sufficient for an agent to use the result. Only the spec fields themselves remain unspecified, a minor gap.

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 both parameters are already documented with examples in the schema. The description only implicitly references the region parameter via 'per region' and adds no format or syntax beyond what the schema provides, so 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+resource (specs of ONE Azure VM size) with clear scope, distinguishing it from the plural find_vm_sizes by emphasizing a single-size lookup. It doesn't explicitly name siblings, but the singular framing and price focus make the purpose unambiguous.

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?

Usage is implied by 'one Azure VM size,' which signals a single-size detail lookup rather than discovery or estimation. However, it never states when to use this versus estimate_vm_cost or find_vm_sizes, and offers no exclusions or prerequisites.

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