exchange_get_role_groups

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

The verb 'List' signals a read-only operation with no side effects, and the parenthetical clarifies that the output is permission-related. With no annotations provided, this is enough context for a parameterless list operation, though it does not disclose pagination or exact return fields—minor gaps for such a simple tool.

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, front-loaded, information-dense phrase. Every word adds value: 'List' communicates the operation, 'role groups' the resource, and 'RBAC — Permissions' the contextual category.

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 parameterless list operation, the description is largely complete: it names the resource and the domain. It does not mention return value shape or whether all role groups are returned, but given the low complexity and absence of parameters, these are acceptable omissions.

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 input schema has zero parameters, so there is no parameter meaning for the description to add. The baseline for 0-parameter tools is 4, and the description correctly focuses on the tool's purpose rather than inventing unnecessary parameter detail.

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 ('List') and resource ('role groups'), and the parenthetical 'RBAC — Permissions' clarifies the domain. This cleanly distinguishes it from the many other exchange_list_* sibling tools that deal with mailboxes, groups, connectors, or domains.

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 explicit when-to-use or alternative guidance is provided, but the resource name makes the use case inferable: enumerate RBAC permission groups. Among the sibling tools there is no competing role-group listing tool, so the lack of an explicit alternative is not a major issue.

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