unlock

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

Discloses key derivation details (PBKDF2, iterations, cipher) and error behavior on wrong PIN. No annotations exist, so description carries full burden. Could mention if multiple unlock calls are allowed.

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 efficient sentences, front-loaded with purpose, then algorithm and consequences. No extraneous information.

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?

Missing prerequisite information (e.g., whether 'init' must be called first). With siblings like init, this is a notable gap. Otherwise covers effect and lifecycle well.

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 has 0% description coverage, but description explains that pin is used with salt to derive the key and that wrong pin returns an error. Adds significant meaning beyond the raw 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 tool unlocks the vault for a session, distinguishes from siblings like lock and init. Specifies the algorithm used and the effect on other tool availability.

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?

Provides context on when to use (before other operations) and lifecycle (until lock or process exit). However, does not explicitly state when not to use or mention alternatives like init.

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