Bulk public keys

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

The description says 'fetch', implying a read operation, yet annotations declare readOnlyHint=false, a mismatch an agent must resolve. Beyond this inconsistency it says nothing about authorization requirements, whether keys of deleted/locked users are included, or behavior for missing ids, though openWorldHint and destructiveHint=false are separately provided in 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?

A single efficient sentence with no filler, front-loading the operation and resource. It is appropriately short, though that brevity contributes to the semantic gaps noted elsewhere.

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, 0% parameter coverage, and four opaque parameters, the description does not provide enough to call the tool correctly. An agent cannot determine where to pass user ids, what the response shape is, or how partial failures are handled.

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 properties (form, params, json_body) are opaque untyped blobs. The description mentions 'a list of user ids' but never maps that to any parameter (only org_id is required and undocumented), leaving the actual user-id payload location ambiguous.

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 (bulk-fetch) and resource (public keys) with scope (for a list of user ids). However, it does not distinguish itself from sibling read tools like vaultwarden_get_public_keys, vaultwarden_get_organization_public_key, and vaultwarden_get_organization_keys, so an agent cannot easily tell which key-fetching tool to choose.

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 description gives no guidance on when to use this bulk variant versus the singular get_public_keys or the organization-scoped key tools. No prerequisites, no when-not conditions, and no alternatives are named despite many closely related siblings.

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