assign-role-to-group

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

No annotations are provided, and the description only states the assignment action without disclosing behavioral traits such as idempotency, permission requirements, or response behavior. The clientId vs realm role distinction is parameter semantics, not behavioral transparency.

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?

One clear, front-loaded sentence that fully conveys the core purpose and the key conditional. No filler or redundant content.

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 assignment operation, the description covers the core purpose with 4 parameters and no output schema. However, it omits behavioral details like idempotency or expected response status, which an agent might need to know to confirm success.

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 the schema already documents all parameters. The description reiterates the clientId/realm role distinction but adds no new meaning beyond the schema; baseline 3 is appropriate.

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), the resource (a role to a group), and distinguishes between realm and client roles via the clientId condition. It also differentiates from sibling tools like assign-role-to-user by specifying the target is a group.

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 explicitly explains when to use clientId (for client roles) vs omit it (for realm roles), providing clear context for parameter usage. It does not explicitly mention alternatives or exclusions, but the target audience (a group vs a user) is implicitly clear from the tool name and sibling set.

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