Disable authenticator

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds only the 'TOTP' qualifier and does not disclose auth requirements, whether disabling is reversible, what user target is affected, or other operational side effects beyond the annotations.

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 only a short phrase and is front-loaded, but it is underspecified for a security-sensitive mutation tool rather than appropriately concise. It does not use the available space to add required context.

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?

Given a mutation tool with three undocumented parameters, no output schema, and minimal annotations, the description is not complete enough. It omits target-user details, permission requirements, and the effect of disabling TOTP.

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?

The schema has 3 parameters with 0% description coverage, all generic fields named form, params, and json_body. The description does not explain any parameter's meaning, format, or which values are expected.

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 TOTP 2FA'. It is clear what operation is performed, but it does not distinguish this tool from adjacent siblings such as vaultwarden_disable_twofactor, vaultwarden_disable_twofactor_put, or vaultwarden_remove_2fa.

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 this tool should be used versus alternatives like disable_twofactor or remove_2fa. No prerequisites, scope, or exclusions are mentioned.

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