Get folders

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that - no note about scoping (personal vs. organization folders), pagination, or result shape - so it contributes no behavioral context of its own.

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?

A single front-loaded sentence with no waste, which is good structurally. But the brevity is under-specification rather than disciplined conciseness for a tool with undocumented parameters and no output schema.

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?

With no output schema, the description should describe what the folder list returns (fields, pagination, ordering). It instead says only 'List all folders', and gives no hint about the three wrapper parameters, leaving the agent under-informed for correct invocation.

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?

All three parameters (form, params, json_body) have 0% schema description coverage and no meaning is conveyed in the description. Since these are generic wrapper parameters whose purpose is not self-evident, the description should compensate but does not.

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?

States a clear verb ('List') and resource ('all folders'), so an agent knows it returns the folder collection. However, it offers no differentiation from close siblings such as vaultwarden_folders_list_folders, vaultwarden_get_folder, or vaultwarden_get_groups, leaving ambiguity about which listing tool to choose.

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 versus the near-identical vaultwarden_folders_list_folders or the singular vaultwarden_get_folder. No prerequisites, auth context, or exclusions are given.

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