Post groups

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

Annotations already indicate this is a non-read-only, non-destructive, open-world operation. The description adds no behavioral context beyond the word 'Create'—it does not explain what a group contains, whether the operation is idempotent, what permissions are required, or what happens on duplicate group names.

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 sentence is extremely short and front-loaded with no filler, but it is under-specified rather than appropriately concise. It lacks the structure needed to convey required inputs or usage context.

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 create endpoint with four undocumented parameters, no output schema, and only generic annotations, the description is completely inadequate. An agent cannot determine what payload shape to send or what organization-level context is required.

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 description provides no parameter information at all. Four parameters including ambiguous names like 'form', 'params', and 'json_body' remain entirely undocumented, and the required org_id is unexplained.

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 ('Create a group'), so the basic action is unambiguous. However, it does not distinguish this tool from nearby siblings such as vaultwarden_post_group, vaultwarden_put_group, or vaultwarden_bulk_delete_groups.

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 many other group-related endpoints, no prerequisites such as admin permissions or organization membership, and no exclusions. The required org_id parameter is not explained.

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