Delete sso user

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is carried. The description adds real value with the post-condition that the account reverts to password login (i.e., the user is not deleted and remains accessible), but it omits permission requirements and whether the SSO link can be re-established.

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 short clause with the key effect front-loaded and no filler. Nothing is wasted.

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 destructive, admin-level mutation with four undocumented parameters and no output schema, the description is too thin: it says what happens but not who may call it, what the arguments mean, or what to do if the user has no SSO link.

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% for 4 parameters. The description never mentions user_id or explains the opaque form/params/json_body properties, so it leaves the agent to guess at the shape of every argument.

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+resource ('Unlink a user's SSO identity') with a clarifying outcome ('force back to password login') that disambiguates it from the many sibling delete tools such as vaultwarden_delete_user. Does not name siblings explicitly, so not a 5.

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?

No when-to-use or when-not-to-use guidance, no mention of required privileges, and no pointer to alternatives like deauth_user or delete_user. The agent must infer selection criteria from the name alone.

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