Put reset password

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds only 'admin-initiated' context and does not explain what state is changed, whether the reset is merely staged or completed, what auth requirements apply, or any side effects.

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, but its brevity reflects under-specification rather than efficient front-loading. The single fragment 'Alias/step of admin-initiated password reset' does not establish a usable structure for selecting or invoking the tool.

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?

This is a five-parameter mutation tool with 0% schema description coverage and no output schema. The description is far too thin to make the tool safely and correctly invocable, especially given nearby reset-password and enrollment siblings.

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 mentions none of the five parameters, including the required org_id and member_id. The schema leaves form, params, and json_body completely undocumented, and the description does nothing to compensate.

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 is a fragment that says 'Alias/step of admin-initiated password reset' but does not clearly state what this tool actually does, whether it initiates, enrolls, completes, or aliases a reset step. It is close to restating the name and does not sufficiently distinguish it from close siblings such as vaultwarden_put_reset_password_enrollment or vaultwarden_get_reset_password_details.

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, when not to use it, or which sibling to prefer for reset-password workflows. The phrase 'admin-initiated password reset' implies a context but does not give an agent actionable routing criteria.

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