Vaultwarden Metadata

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

With no annotations, the description carries the full burden. It discloses meaningful behavior: the snapshot returns opaque identifiers, type codes, lifecycle timestamps, counts and typed relationships, and it states that commit authority lives elsewhere and backfeed is unsupported. It omits permissions, rate limits, and side-effect profile, so the disclosure is partial rather than rich.

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 opening sentence is front-loaded and the middle paragraph is dense but informative, yet the trailing 'CONCEPT:VW-KG.ingest.metadata-only' token is cryptic and does little work for an agent. Length is moderate, but the jargon density reduces effective conciseness.

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?

An output schema exists, so return values need not be spelled out, and the two-parameter surface is small. The definition is adequate but leaves the schema-listed backfeed_metadata action in tension with its claim that backfeed is 'explicitly unsupported', and it provides no sibling-routing context, so it falls short of complete for an agent choosing among nine vaultwarden tools.

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 100%, so the schema already documents 'action' and 'params_json', establishing the baseline of 3. The description names metadata_snapshot and backfeed_metadata, but adds no syntax or payload detail for params_json beyond what the schema provides. No extra value beyond structured fields.

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 gives a verb and resource ('Serve the certified metadata-only source projection') and lists what metadata_snapshot returns, but the phrasing is heavily jargon-laden and never plainly states what the tool is for. It does not distinguish this tool from siblings like vaultwarden_system or vaultwarden_maintenance, leaving the agent to infer the boundary.

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?

It does communicate some directional guidance: commit/checkpoint/reconcile belongs to source_sync, and backfeed is unsupported. However, there is no explicit when-to-use statement relative to the eight sibling tools; the agent must infer that this is the metadata-projection read path. Implied usage only.

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