Create Folder

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

Annotations readOnlyHint=false and destructiveHint=false indicate a mutation but not destructive. The description adds that it creates a personal folder, which clarifies the scope. No contradictions, but lacks details on naming constraints or uniqueness expectations.

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 front-loaded purpose. No unnecessary information; every word adds value.

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 simple creation tool with one parameter and no output schema, the description covers purpose and usage. However, it does not mention what the tool returns after creation (e.g., the folder object or success message), which could be helpful for an AI agent.

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 a description for the 'name' parameter. The description reinforces that it's a personal folder but does not add new semantics beyond the schema's 'Display name for the personal folder.' 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?

Clearly states it creates a personal Bitwarden folder, distinguishing it from organizational collections. The verb 'Create' and resource 'personal Bitwarden folder' are specific, and it differentiates from sibling tool keychain_create_org_collection by specifying 'outside organization collections'.

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?

Explicitly says 'Use this to organize items outside organization collections,' providing clear context for when to use this tool and implicitly pointing to the alternative keychain_create_org_collection for organization collections.

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