Post delete organization

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description repeats 'Delete' and notes the POST alias, but adds no detail about irreversibility, what related data is removed, required permissions, or confirmation behavior beyond 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 extremely short and front-loads the core action. The parenthetical is terse but useful for identifying the alias variant; however, the overall definition is so minimal that concision comes at the cost of completeness.

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?

This is a destructive organization deletion tool with four parameters, no schema descriptions, and no output schema. The annotations cover the safety profile, but the description still lacks parameter explanations, side effects, and prerequisite/authorization context needed for an agent to invoke it confidently.

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?

The schema has four parameters with 0% description coverage, including a required org_id and opaque form, params, and json_body fields. The description mentions none of these and provides no compensating meaning about what values to supply.

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 an organization'. The '(POST alias)' parenthetical clarifies that this is an HTTP POST alias variant, but it does not explain how this differs from sibling delete-organization tools such as vaultwarden_admin_delete_organization or vaultwarden_organizations_delete_organization.

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 tool versus the other delete-organization variants, nor are there any exclusions, prerequisites, or confirmation requirements. The only implied usage is that the caller wants to delete an organization.

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