Sync

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description usefully discloses what the returned payload contains (valuable given no output schema), but it never explains why a 'sync' is not read-only — i.e., what server-side state (sync tokens, timestamps) may be touched — nor any auth or rate-limit considerations.

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 dense clause that front-loads the scope and then lists contents; nothing is padded. It is a fragment rather than a sentence, which costs a little readability but no information.

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?

The description compensates well for the missing output schema by enumerating returned entity types, but it leaves four opaque parameters unexplained and offers no hint about the mutation implied by readOnlyHint=false. For a tool whose call signature is entirely undescribed, this is not enough.

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 coverage is 0%: four parameters (data, form, params, json_body) are completely untyped and undocumented, and the description adds nothing about them. The only mitigating factor is that all are optional with null defaults, so a parameterless call is plausible, but the agent has no way to know which of the four to populate.

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 names a specific verb+resource ('Full vault sync') and enumerates the payload contents (ciphers, folders, collections, sends, org/policy/domain metadata). It implicitly separates itself from narrow siblings like vaultwarden_get_ciphers or vaultwarden_get_folders by being the 'full ... in one payload' variant, though it never names an alternative.

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 statement of when to use this versus the many per-resource list tools (vaultwarden_get_ciphers, vaultwarden_get_folders, vaultwarden_get_org_collections, vaultwarden_get_sends). The word 'Full' hints at a bulk alternative, but no prerequisites, exclusions, or cost/completeness trade-offs are given.

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