Contract Testing: Admin Remove Role from User

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

Description says 'Remove' indicating a mutation, but annotations include readOnlyHint: true and destructiveHint: false. This is a direct contradiction. The description fails to clarify the actual behavior, leaving the agent confused.

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?

Description is very short, but it redundantly lists parameters already in schema. It is structured but not optimized; the parameter list takes space without adding 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 tool, the description is incomplete. It does not explain the contradiction between 'remove' and readOnlyHint, nor does it mention success/error responses. Without output schema, the agent lacks expectation of return values.

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 covers 100% of parameters with descriptions. The description restates parameter names but adds no additional meaning or constraints beyond what the schema provides.

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?

Description clearly states the verb 'remove' and the resource 'single role' from a user. It distinguishes from sibling tools like 'admin_add_role_to_user'. However, it restates the tool's name with little added specificity.

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 versus alternatives like 'admin_add_role_to_user' or 'admin_set_user_roles'. The description does not mention prerequisites or when not to use it.

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