Backup db

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

Annotations already declare a non-read-only, non-destructive, open-world operation, so the safety profile is partly covered. The description adds the sqlite-only precondition, which is real context, but says nothing about admin privileges required, whether the backup is synchronous or async, where the file is written, or what the response contains.

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 eight-word sentence with the constraint parenthesized at the end — zero waste and front-loaded. It is defensibly efficient, though bordering on under-specified for a mutating admin operation.

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 state-changing backup trigger with no output schema, three undocumented parameters, and no stated auth or async behavior, the description leaves too much unknown. An agent cannot predict the effect, the wait time, or the return value from this text alone.

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 three parameters (form, params, json_body) are opaque generic passthrough wrappers with no explanation anywhere. The description does not mention parameters at all; at best 'on-demand trigger' implies the call is effectively parameterless, but it never clarifies what the passthrough fields mean or whether any are needed.

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 (Trigger) and resource (on-demand database backup) plus an environment constraint (sqlite only), so an agent immediately knows what happens. It is clear but does not position itself relative to any of the many sibling administrative tools, though none of them appear to be backups.

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 '(sqlite only)' qualifier is a genuine applicability condition that tells the agent when this tool will work. However, there is no explicit when-to-use guidance versus alternatives (e.g. scheduled/automatic backups, or the other maintenance tools like vaultwarden_maintenance_plan_deduplication), and no prerequisites are stated.

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