find_available_regions

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

No annotations provided, so description carries full burden. Discloses 'cheapest first' ordering and that region in spec is overridden. Lacks mentions of rate limits, auth, or edge cases (e.g., behavior when service not found).

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?

Concise, front-loaded with main purpose. Each sentence adds value: purpose, spec reuse, region usage, baseline option. No extraneous text.

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?

Given three parameters (one required, one nested object) and an output schema, description covers key aspects. Does not explain output schema structure but that is handled by schema itself. Suffers slightly from missing explicit sibling usage guidance.

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%, but description compensates by explaining spec as 'same as get_price' and region override, regions parameter usage, and baseline_region purpose. Could further detail spec structure, but references get_price as baseline.

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?

Clearly states 'Find all regions where a specific service/instance type is available, cheapest first.' Uses specific verb-resource pair and ordering, differentiating from siblings like find_cheapest_region (which returns only the cheapest) and compare_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?

Provides explicit guidance on spec parameter (same as get_price, region overridden) and regions parameter (omit for major, 'all' for full scan). Mentions baseline_region for delta comparison. Missing explicit differentiation from siblings like find_cheapest_region or compare_prices.

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