Finds Azure role assignments linked to unresolved principals, revealing orphaned permissions. Helps audit RBAC by listing assignments where the principal is missing from the tenant.
Lista role assignments órfãos (principal não resolvido no tenant visível).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds one useful behavioral detail: orphan is defined as unresolved principal within the visible tenant. It does not contradict the annotations and provides some context beyond them, but nothing more substantial.
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, focused sentence that defines the tool's purpose and its key qualifier without any filler. It is efficiently front-loaded with the action and resource.
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?
The description is adequate for a simple read-only list tool with annotations that already provide safety and open-world context. However, with no output schema and no mention of return values, pagination, or how limit affects results, there are minor gaps for an agent selecting and invoking the tool.
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%, and the description does not mention the only parameter, limit. The parameter name is somewhat self-explanatory, but the description adds no meaning about pagination, maximum values, or behavior when omitted.
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 ('Lista'), a specific resource ('role assignments órfãos'), and defines the key concept in parentheses ('principal não resolvido no tenant visível'). This clearly distinguishes it from the sibling list_azure_role_assignments by focusing on orphaned assignments.
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 intended use is implied: call this when you need role assignments whose principal cannot be resolved in the visible tenant. However, it does not explicitly mention alternatives like list_azure_role_assignments or state when not to use this tool, so guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.