unlock

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

Discloses key behaviors: prompts via native OS dialog, password never exposed to MCP/LLM, not supported in headless environments. No annotations provided, so description carries full burden and does so completely.

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?

Three sentences, no fluff. Each sentence adds essential information: action, parameterless nature, security detail, and usage constraint. Front-loaded with core purpose.

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?

Tool is simple (no params, no output schema). Description covers purpose, usage context, security, and alternatives. No gaps remain for an 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?

Input schema has 0 parameters with 100% coverage. Description redundantly confirms 'takes no parameters' and adds rationale (password handled via dialog). Adds value beyond schema.

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 the verb 'Unlock' and resource 'Bitwarden vault'. Description distinguishes from sibling 'lock' and provides specific scope (no parameters, prompts for master password).

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 describes when to use (unlock vault) and when not to (headless/non-interactive, alternative manual command). Provides direct alternative: 'run bw unlock --raw manually and set BW_SESSION'.

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