list_directory_role_assignments

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it only says "List," which implies read-only behavior without stating it. It does not mention pagination behavior despite the `top` parameter, authentication or privileged-role requirements implied by PIM adjacency, or what is returned. This is bare-minimum disclosure for a tool with no annotation safety net.

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 sentence with the verb and resource up front, so it is certainly concise. However, the only extra content, "(PIM-adjacent)," is vague and does little work, making the brevity border on under-specification rather than efficient communication.

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 tool is simple (zero required parameters, no nested objects), which lowers the completeness burden, but there is no output schema and no annotations to fill gaps. The description fails to explain parameter semantics, return shape, or permission expectations, leaving the agent to guess on the two parameters and the response format.

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%, so the description must compensate for the undocumented `top` and `filter` parameters, but it says nothing about them. The agent has no hint that `top` likely controls page size or that `filter` likely expects OData filter syntax. No parameter meaning is conveyed by either the schema or the description.

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") and resource ("Entra ID directory role assignments"), clearly identifying what the tool does. The resource term "assignments" distinguishes it from siblings like list_directory_roles and list_directory_role_members. However, it does not explicitly differentiate itself from those siblings or explain what an assignment is versus a role member, so it stops short of full clarity.

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 such as list_directory_roles, list_directory_role_members, or list_directory_role_definitions. The parenthetical "PIM-adjacent" is a weak hint at the domain but does not state when to prefer this tool or when to avoid it. No exclusions or conditions are given.

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