manage_azure_ad_roles

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, which already inform the agent this is a mutable, non-idempotent operation with potential destructive effects. The description adds context about managing 'privilege escalation controls' which suggests security implications, but doesn't elaborate on specific behaviors like what gets destroyed, authentication requirements, or rate limits. No contradiction with annotations exists.

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, efficient sentence that clearly states the tool's scope. It's appropriately sized for a multi-action tool and front-loads the key information without unnecessary elaboration. Every word contributes to understanding the tool's domain, though it could be slightly more specific about the 'manage' verb.

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 tool with 5 parameters, no output schema, and annotations covering safety profile, the description is minimally adequate. It defines the domain but lacks details on return values, error conditions, or operational constraints. The combination of good schema coverage and annotations helps, but the description itself doesn't provide complete context for safe and effective use, especially given the destructive nature hinted by annotations.

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 100%, with all parameters well-documented in the schema itself (e.g., action with enum values, roleId, principalId). The description mentions 'role assignments, custom roles, and privilege escalation controls' which loosely maps to some parameters but doesn't add meaningful semantic detail beyond what the schema provides. The baseline of 3 is appropriate given the comprehensive schema documentation.

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 tool manages Azure AD administrative roles with specific components (role assignments, custom roles, privilege escalation controls). It distinguishes from many siblings like manage_azure_ad_apps or manage_azure_ad_devices by focusing on roles, but doesn't explicitly differentiate from all potential role-related tools. The verb 'manage' is somewhat broad but the resource scope is well-defined.

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. It doesn't mention prerequisites, appropriate contexts, or compare with sibling tools like manage_security_groups or manage_service_principals that might overlap in identity management. The agent must infer usage solely from the tool name and description without explicit direction.

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