Create Users Reset Password

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

With no annotations provided, the description carries the full burden, but it only discloses that a password reset occurs. It does not mention side effects, such as whether existing sessions are invalidated, whether the token is required and authenticated, or what happens if password and passwordConfirm do not match.

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 concise and free of fluff, which is good, but it is too terse to be appropriately sized for a tool with four required parameters and no annotation or schema descriptions. It sacrifices necessary context for brevity.

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?

The description is drastically incomplete. An agent would not know that a token is likely obtained via a prior forgot-password step, whether email is used for lookup, or how passwordConfirm validates the new password. There is also no output schema or annotations to compensate.

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 0% and the description adds no meaning to the four required parameters. The roles of token, email, password, and passwordConfirm are completely unexplained, including the crucial relationship between password and passwordConfirm.

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 clear action—'Resets the user password'—with a specific verb and resource. However, it does not distinguish this from sibling tools like update_users_password or create_users_forgot_password, and it omits the reset-token context that would make the purpose fully precise.

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 about when to use this tool versus alternatives. The description does not mention that this is likely the completion step of a password-reset flow, nor does it explain scenarios where update_users_password or create_admin_users_password_reset_token should be used instead.

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