Post set password

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the write/open-world nature is covered. The description adds the provisioning-lifecycle context, which is genuinely useful, but says nothing about authentication required, irreversibility of setting a master password, or what the request body must carry.

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?

A single front-loaded sentence with no filler. It is efficient, though the terse parenthetical is the only thing standing between this and an under-specified label.

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 security-sensitive mutation with three opaque, undocumented parameters and no output schema, the description is far too thin. An agent cannot determine what to put in json_body or whether the call is safe to repeat, which is the information the description should be carrying here.

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 coverage is 0% and the three parameters (form, params, json_body) are untyped with null defaults, so the schema supplies essentially no meaning. The description provides no parameter guidance at all, leaving the agent with no idea that a password hash, KDF config, and user key are typically required for this endpoint.

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?

States a specific verb and resource ('Set initial master password') and adds scoping context that the name doesn't carry: it is the initial password set during post-SSO/key-connector provisioning. It is distinguishable from siblings like vaultwarden_put_reset_password and vaultwarden_post_password by the 'initial provision' framing, though it never names those siblings explicitly.

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 parenthetical 'post-SSO/key-connector account provisioning' implies the when: only for freshly provisioned accounts that have no master password yet. However, no explicit exclusions are stated (e.g. don't use for a user-initiated password change, use put_reset_password/put_remove_password instead), so the agent must infer the boundary.

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