Post folder

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

Annotations already declare this is a non-read-only, non-destructive mutation with openWorldHint=true. The description adds that the operation renames a folder and is a POST alias, but does not disclose permission requirements, side effects, or error behavior beyond what annotations provide. No contradiction with 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 a single front-loaded sentence with no wasted words. It is appropriately terse, though its brevity contributes to missing detail rather than being a structural flaw.

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 mutation tool with four parameters, 0% schema description coverage, and no output schema, the description is too sparse. Annotations cover the safety profile, but the definition does not explain parameter usage, required inputs beyond folder_id, or what form/json_body should contain.

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 all four parameters. The description does not explain folder_id, form, params, or json_body, leaving the agent with no semantic guidance beyond the required folder_id name. This is a major gap for a four-parameter mutation tool.

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: 'Rename a folder'. It is clear what the tool does, though it does not explicitly distinguish this from the sibling put_folder or other folder-related tools beyond the vague '(POST alias)' note.

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 explicit guidance on when to use this tool versus alternatives like vaultwarden_put_folder, nor any prerequisites or exclusions. The phrase '(POST alias)' hints at an HTTP-method distinction but does not tell an agent when to choose this over other folder update tools.

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