Post delete group

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

Annotations already mark this as destructive, non-read-only, and open-world. The description adds only the POST-alias detail and does not disclose side effects, cascading effects on group members, permission requirements, or irreversibility beyond what annotations already imply.

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 a single front-loaded sentence with no filler. It is compact and immediately actionable, even though it is under-informative for safe invocation.

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 group-deletion tool with five parameters, no output schema, and zero schema parameter descriptions, the description is too thin. It does not explain required organizational context, parameter roles, or the effect on group membership.

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% for five parameters. The description implies a group identifier but does not explain required org_id versus group_id, nor does it clarify the optional form, params, or json_body parameters.

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 states a specific verb and resource: "Delete a group." The "(POST alias)" note helps distinguish it from the sibling DELETE-style group deletion endpoint, but it does not explicitly name or explain the 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 guidance on when to use this POST alias versus vaultwarden_delete_group or bulk deletion siblings, and no prerequisites or exclusions are provided. The intended usage is only implied by the verb.

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