Bulk restore members

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the agent knows this is a non-destructive mutation against an external system. The description adds nothing beyond that: no statement of which members are affected, how they are identified, whether it requires an admin token, or what happens to already-active members.

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 four-word phrase is concise and technically front-loaded, but it is under-specification rather than concision; every sentence that would earn its place is missing.

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?

A mutation tool with four undocumented parameters, no output schema, and no annotations covering semantics beyond safety hints. The description leaves the agent unable to determine required authorization, the shape of json_body, or the effect/return of the operation.

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 four properties (form, org_id, params, json_body) have no types or descriptions. The description supplies no parameter meaning at all — not even which identifier selects the members to restore, beyond the required org_id.

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?

"Bulk restore revoked members" is essentially a restatement of the title "Bulk restore members" with one qualifier added. It names a verb and resource, but gives no clue how it differs from sibling tools like vaultwarden_restore_member, vaultwarden_restore_member_vnext, or vaultwarden_bulk_revoke_members (the inverse operation).

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 to use this bulk endpoint versus the singular vaultwarden_restore_member/vaultwarden_restore_member_vnext, nor any prerequisite (admin role, org scope, whether members must already be revoked). An agent facing a dozen restore/revoke siblings has nothing to route on.

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