create_role_assignment

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

No annotations provided, so description carries full burden. It correctly indicates the tool creates an RBAC assignment, implying mutation. However, it does not disclose side effects (e.g., permissions required, idempotency, overwrite behavior) or error conditions.

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 concise, with a one-sentence purpose followed by a bulleted list of parameters. No redundant information; each line adds value.

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?

With an output schema present, the description does not need to explain return values. It covers the essential purpose, all parameters, and the relationship between resource_group and scope. Could mention required permissions, but overall complete.

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%, but the description compensates by explaining each parameter: principal_id as 'Object ID of the principal (user, group, or service principal)', role_definition_name with examples, and clarifying the optional scope parameters. This adds significant meaning beyond the schema.

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 'Create a new role assignment (RBAC).' The verb 'Create' and resource 'role assignment' are specific. It distinguishes from siblings like 'delete_role_assignment' and 'list_role_assignments_for_principal'.

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 parameter explanations but does not explicitly state when to use this tool vs alternatives, nor does it mention prerequisites or when not to use it. Usage is implied through context of creating role assignments.

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