list_locations

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

No annotations exist, so the description must fully describe behavior. It states 'list all Azure regions' but does not mention what the output contains (e.g., region names, display names, status). Since an output schema exists, the agent could infer some details, but the description itself lacks behavioral context like read-only nature or pagination.

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 a single sentence that immediately conveys the action and target. It is concise with no filler and follows a front-loaded structure: verb + resource + scope.

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 simple parameterless list operation with an existing output schema, the description covers the essential purpose. It lacks mention of result ordering or filtering, but these are unlikely to be relevant. Overall, it is nearly complete given the low complexity.

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?

There are no parameters. Schema coverage is 100% (vacuously). Baseline for 0 parameters is 4. The description does not add parameter-specific details because none exist, so a score of 4 is appropriate.

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 clearly states 'List all Azure regions available for the subscription.' The verb 'List' and resource 'Azure regions' are specific. The tool is distinct from siblings like aad_create_user or list_vms, which manage resources, while this is a read-only enumeration of regions.

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?

No guidance is provided on when to use this tool, when not to use it, or what alternatives exist. For example, it does not indicate if region availability varies by subscription type or if prerequisites exist. With many sibling tools, this omission increases cognitive load.

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