Delete group

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds no consequence detail such as irreversibility, required admin rights, effect on members, or confirmation needs, and it does not contradict the 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?

The description is only three words, so it is not verbose, but it is under-specified rather than appropriately sized. It has no structure or front-loaded constraints to help an agent invoke the tool correctly.

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 mutation with five undocumented parameters and no output schema, "Delete a group" is not enough to invoke confidently. Annotations cover the safety hint, but the definition omits scope, required IDs, optional payload fields, and side effects.

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?

There are five parameters with 0% schema description coverage, and the description mentions neither org_id/group_id nor the optional form/params/json_body fields. It provides no meaning, format, or constraints to compensate for the missing schema documentation.

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 says "Delete a group", which is a clear verb and resource but exactly restates the tool title/name. It gives no boundary versus vaultwarden_bulk_delete_groups or vaultwarden_post_delete_group, so it is tautological rather than informative.

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 when-to-use, when-not-to-use, or alternative routing. An agent cannot tell from this line whether to use single-group delete instead of the bulk-delete or POST siblings; the description is not misleading, but it provides no guidance.

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