Contract Testing: Admin Add Role to User

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

Annotations already establish the tool is not read-only, not idempotent, and not destructive. The description adds the admin context and single-role semantics, but it does not disclose what happens on duplicate assignment, whether the user or role must already exist, or any side effects beyond the role addition.

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 short and front-loaded with the core action. However, the 'Parameters' block duplicates the schema verbatim, and 'Toolset: Admin' repeats title information, so some lines do not add new 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?

For a simple two-parameter mutation with annotations and full schema coverage, the description is nearly sufficient: an agent can determine the operation, required parameters, and admin context. The main gap is explicit routing guidance versus admin_set_user_roles, but that is more a selection concern than an invocation blocker.

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?

The input schema has 100% description coverage for both parameters, and the description restates the exact schema text for userId and roleId. It adds no new meaning beyond the parameter names, types, required flags, and UUID format already present in 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 states a specific verb ('Add'), resource ('a single role'), and target ('to a user'), plus the admin qualifier. The phrase 'single role' helps distinguish it from sibling admin_set_user_roles, which would set or replace multiple roles.

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 admin_set_user_roles or admin_remove_role_from_user. No preconditions, exclusions, or alternative-selection hints are given; only 'admin' is mentioned, which already appears in the title.

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