get_user_roles

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

No annotations are provided, so the description must carry full disclosure. It only states the action without any behavioral details such as permissions required, failure modes (e.g., user not found), or whether inherited roles are included. This is a minimal read tool, but the description doesn't go beyond the basic purpose.

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 no filler. Every word contributes to the core meaning, making it highly concise and scannable.

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 one-parameter read operation, the description fully specifies what the tool does and the input. The output schema (not shown) can explain return structure. It doesn't mention prerequisites or error behavior, but for this low-complexity tool, the description is adequate.

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 schema has no description for user_id (0% coverage), and the description only says 'by user ID,' which is thin. It doesn't clarify the expected format (e.g., object ID vs UPN) or how to obtain it, though sibling tools like get_user_by_id imply the ID type. The description adds minimal value beyond the parameter name.

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 the action ('Get all directory roles assigned to a user') and the input key ('by user ID'). This distinguishes it from sibling tools like get_user_groups (groups vs roles) and get_user_by_id (user profile vs roles).

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?

It explicitly requires a user ID, making the context clear. It doesn't name alternatives or exclusions, but the resource (directory roles) is distinct from sibling tools, so the intended usage is obvious. Slightly less explicit than naming alternatives.

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