Post password

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

The annotations already disclose readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds important context by specifying that the mutation targets the master password, which is security-sensitive. However, it does not explain authentication requirements, side effects, reversibility, or how the change is performed.

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 a single front-loaded sentence with no wasted words. However, it is too terse for a high-stakes master-password mutation with three undocumented parameters, so its conciseness comes at the cost of necessary detail.

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 definition identifies the operation but lacks critical context for a master-password change: required body structure, authentication expectations, side effects, and relationship to sibling password operations. With no output schema and 0% schema description coverage, the description does not carry enough of the burden.

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 three parameters are generic and undocumented: form, params, and json_body. The description provides no information about what each parameter should contain or how the master password change request is shaped.

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 and resource: 'Change master password.' This is clearer than the title 'Post password' and tells the agent what operation is being performed. However, it does not differentiate from nearby password-related siblings such as vaultwarden_post_set_password, vaultwarden_put_reset_password, or vaultwarden_put_remove_password.

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 gives no guidance on when to use this tool versus the many other password-related tools in the sibling list. It also omits prerequisites such as authentication, current-password requirements, or whether this is self-service versus admin-driven.

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