Delete config

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

Annotations already flag destructiveHint=true and openWorldHint=true, so safety and scope are covered structurally. The description adds genuine value by disclosing the concrete effect: overrides revert to defaults rather than data being hard-deleted. It still omits who can call it, whether the change is reversible or audited, and which configuration layer is affected.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined density.

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 destructive, open-world mutation with three undocumented parameters and no output schema, the description should say which config is reset, who may do it, and what happens on success. None of that is present, so the definition is not sufficient on its own.

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% across three parameters (form, params, json_body) that have no titles or types beyond defaults of null. The description provides zero guidance on what these carry or which configuration overrides are targeted, so an agent cannot construct a valid call from the definition alone.

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 verb 'reset' plus the object 'configuration overrides' gives a workable action, and 'back to defaults' clarifies the effect of the deletion. However, it is not distinguished from sibling tools like vaultwarden_config or vaultwarden_admin, and the tool name (delete_config) uses a different verb than the description (reset), which can confuse an agent about whether state is removed or restored.

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 indication of when this should be invoked versus vaultwarden_config or vaultwarden_admin, nor any prerequisites (admin rights, which configuration scope, environment impact). Usage must be inferred entirely from the tool name and annotations.

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