Edit Folder

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

Annotations indicate a mutation but non-destructive operation. The description adds value by specifying 'mutates only folder metadata, not the items inside it' and 'returns the updated folder id/name summary.' This discloses scope and output beyond 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?

Two concise sentences with no redundant words. The first sentence states the core action, and the second adds scope and return summary. Information is front-loaded and 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?

The tool is simple (2 required params, no output schema, non-destructive). The description covers purpose, scope (metadata only), and return value. No gaps given the tool's complexity.

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 coverage is 100% with clear descriptions for id and name. The description repeats the id retrieval context ('by id') and mentions 'new display name' but adds little extra meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states 'Rename an existing personal Bitwarden folder by id.' The verb 'rename' is specific, the resource is a personal folder, and the method (by id) is explicit. It distinguishes from sibling tools like keychain_create_folder and keychain_delete_folder.

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?

The description implicitly defines when to use: when you need to rename a folder, not to modify items inside. It does not explicitly list alternatives or when not to use, but the context is clear. Among siblings, no other tool renames folders, so differentiation is inherent.

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