Contract Testing: Admin Remove Role from User

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

The description only repeats that the tool removes a role, which aligns with the destructiveHint annotation. It adds no additional behavioral insights such as error conditions, permission requirements, or side effects. The annotation already covers destructiveness and idempotency, so the description adds minimal value.

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 to the point, with the key action in the first sentence. However, it redundantly lists parameter details already in the schema. This is slightly inefficient but not rambling.

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 destructive tool with no output schema, the description should explain expected outcomes (e.g., success confirmation) or error cases. It does not. Given the tool's simplicity (2 required params), the lack of return value info and usage context makes it insufficient for complete agent understanding.

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 already provides full descriptions for both parameters (userId, roleId) with 100% coverage. The description redundantly restates these, adding no new meaning. Per guidelines, baseline is 3 when schema coverage is high, and no extra semantics are provided.

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 verb 'Remove' and the resource 'a single role from a user', and the '(admin)' context distinguishes it from non-admin tools. It helps differentiate from sibling tools like admin_add_role_to_user, admin_set_user_roles, and admin_reset_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?

The description provides no guidance on when to use this tool versus alternatives (e.g., admin_set_user_roles). It does not mention prerequisites, constraints, or exclusions. The bare action statement offers no usage context.

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