azure_compare_vm_prices

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says the tool compares VM SKUs and implies a follow-up call; it does not state whether the operation is read-only, what output format to expect, how results are ordered, or any side effects/limitations.

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 that waste no words. The primary purpose is front-loaded, and the critical follow-up instruction is concise and actionable.

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 straightforward read-only comparison tool, the description is serviceable: it names the action, the key inputs (VM SKUs, regions), and a necessary follow-up. However, with no output schema and no annotations, it omits return-value semantics, output ordering, and any caveats about pricing data completeness or regional availability.

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?

The schema already documents the two required parameters with examples and provides an enum/default for response_format. The description adds no parameter-specific detail. With only 50% schema coverage, optional parameters like currencyCode rely on naming and defaults, but this is acceptable for a simple compare tool.

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 and resource: 'Compare VM SKUs across regions.' This clearly conveys the tool's core function and distinguishes it from the reservation-vs-payg follow-up tool, though it does not explicitly contrast it with sibling search/find-cheapest tools.

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 description provides clear workflow guidance: 'Always call azure_compare_reservation_vs_payg after for workloads running >6 months.' This gives a concrete condition for using a sibling tool. However, it does not explain when to choose this tool over azure_search_prices or azure_find_cheapest_region.

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