create_authz_role_assignment

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

With no annotations, the description must disclose behavioral traits. It only states the basic action. Missing details: idempotency (can the same assignment be made twice?), what happens if the user already has the role, required permissions, and whether the assignment overwrites or adds. The optional domain scope is mentioned but not elaborated (e.g., whether domain_id is required when domain_type is set).

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: 'Assign a role to a user, optionally scoped to a domain.' It is concise and contains no wasted words, directly stating the tool's function.

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 has 4 parameters and no output schema. The description is incomplete for safe usage: it does not explain that both user and role must already exist, whether the assignment is idempotent, what are valid domain types, or error conditions. Given no annotations, the description should provide more behavioral context.

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%, so baseline is 3. The description adds no extra semantic value beyond the schema. It reiterates the optional domain scope, but the schema already describes the parameters with similar wording. No additional context about parameter relationships or validation.

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: 'Assign a role to a user, optionally scoped to a domain.' It uses a specific verb ('assign') and identifies the resource ('role to a user'), distinguishing it from sibling tools like 'create_authz_role' (which creates a role definition) and 'delete_authz_role_assignment'.

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?

No guidance on when to use this tool vs alternatives, such as when to scope by domain or when not to. No mention of prerequisites (e.g., user and role must exist) or typical use cases. The description lacks any 'when-to-use' or 'when-not-to-use' context.

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