Vaultwarden Organizations

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

With no annotations, the description carries the full burden. It discloses the dispatch-by-route-name mechanism, but nothing about mutation vs read behavior, destructive operations (org/policy deletion, LDAP import), authentication or server-config prerequisites, or rate limits — significant gaps for a dispatcher spanning dozens of write routes.

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?

Short and front-loaded: coverage statement first, dispatch mechanism second. The trailing 'CONCEPT:' token is noise, and the 'plus the public LDAP import and misc...' clause is dense, but overall it is efficient.

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?

An output schema exists, so return values need not be described. However, for an unannotated mega-dispatcher over read and write routes, the description omits the operational prerequisites and safety context an agent needs before firing it, leaving it only minimally adequate.

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 100%, so the schema already explains 'action' as a Route.name and 'params_json' as path/query parameters. The description adds only the general dispatch concept and does not clarify param_json shape for specific actions, so baseline 3 applies.

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?

It names a concrete verb ('Manage') plus the resource families (organizations, collections, members, groups, policies, plus public LDAP and misc routes) and states the dispatch mechanism by route name. The domain enumeration implicitly separates it from siblings like vaultwarden_ciphers or vaultwarden_sends, though it never explicitly contrasts them.

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?

No statement of when to use this tool versus siblings. The claim to also cover 'public' and 'misc server-settings/HIBP routes' actively blurs the boundary against vaultwarden_system and vaultwarden_maintenance without resolving which one wins. The only usage hint (action='list_actions') lives in the schema, not the description.

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