Disable twofactor

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

Annotations already say readOnlyHint=false and destructiveHint=false, so the mutation profile is partially covered. The description adds nothing about authorization requirements, irreversibility, whether the user is notified, or what happens to backup codes/sessions when a 2FA provider is disabled.

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 single short sentence is front-loaded and free of filler. It is not verbose, though it is so terse that it omits useful structure rather than being overlong.

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?

With no output schema, no parameter documentation, and no meaningful annotation explanation, the description is not complete enough for a security-sensitive mutation tool. It does not tell an agent how to specify the provider or what changes result from the call.

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 (form, params, json_body) are opaque and untyped beyond null defaults. The description does not identify a provider parameter, nor explain how the provider is specified, so it fails to compensate for the empty schema.

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 ("Disable a specific 2FA provider"), but it does not distinguish this tool from close siblings such as vaultwarden_disable_twofactor_put, vaultwarden_disable_authenticator, or vaultwarden_remove_2fa. An agent cannot tell which of those to use from the description alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase "specific 2FA provider" implies selection but never says how that selection is supplied or when this tool is preferred over related disable/remove tools.

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