list_management_groups

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action (list) but does not mention read-only nature, required permissions, pagination behavior, or any side effects. For a list operation, these details are minimal but still absent.

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 of six words, front-loading the critical information. Every word contributes meaning. There is no fluff or repetition. It is appropriately sized for a simple parameterless tool.

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 the tool's simplicity (zero parameters, output schema present), the description covers the essential purpose. However, it could be more complete by noting that it lists management groups accessible to the caller or mentioning any hierarchical scope. The presence of sibling tools also suggests that a brief differentiation would improve completeness.

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 tool has zero parameters, so the schema coverage is 100%. Baseline is 4 per guidelines. The description does not need to add parameter info, but it could clarify the implied context (e.g., scope of listing). It adds no extra semantic value beyond the schema, but this is acceptable given no parameters.

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 uses a specific verb "List" combined with the resource "all Azure management groups", clearly distinguishing it from sibling tools like "get_management_group" which targets a single group. It explicitly states its scope, leaving no ambiguity about what the tool does.

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 no guidance on when to use this tool versus alternatives (e.g., get_management_group for a specific group). It lacks any context about prerequisites or typical scenarios, which is a gap given the numerous sibling tools in the same domain.

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