Contract Testing: Admin Set User Roles

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

The description claims to 'Replace all roles' (a write operation), but the annotations declare readOnlyHint=true. This is a serious contradiction. Additionally, no behavioral details about authorization, reversibility, or side effects are provided, which is expected given the conflicting annotations.

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 very short, but it is front-loaded with the key action. However, it lacks structure such as ordering of parameters or usage notes. It is concise but at the expense of completeness.

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?

Given the tool modifies user roles and lacks an output schema, the description should explain return values or effects. It does not. Sibling tools like 'admin_get_user' exist but no distinction is made. The description is insufficient for an agent to fully understand the tool's behavior.

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 coverage is 100%, and the description repeats the parameter names and types ('UUID', 'Array of role UUIDs') already present in the schema. No additional semantic value is added, meeting the baseline expectation but not exceeding it.

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 'Replace all roles assigned to a user (admin)', which is a specific action on a resource. However, it does not explicitly differentiate from sibling tools like 'admin_add_role_to_user' or 'admin_remove_role_from_user', but the name and description sufficiently convey the overwrite behavior.

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?

There is no guidance on when to use this tool versus other role management tools, nor any mention of prerequisites or exclusions. The description simply states what it does without context for selection.

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