vault_unlock

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool unlocks the vault with a passphrase, but does not describe failure modes (e.g., wrong passphrase), timeout, or side effects. The behavioral context is minimal but sufficient for a simple unlock action.

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 one sentence that front-loads the verb 'Unlock' and clearly states the purpose. It contains no extraneous words and efficiently conveys the tool's function.

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?

Given the simple nature of the tool (one required parameter, no output schema, no annotations), the description is largely complete. It explains the action and prerequisite relationship. However, it could explicitly note that the vault remains unlocked until vault_lock is called for better completeness.

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 for the single parameter 'passphrase' is 100%, and the schema itself describes it as 'Vault passphrase'. The description adds no additional meaning beyond what the schema provides, earning a baseline score of 3.

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 the action (unlock) and the resource (secrets vault), and specifies it is required before storing or using credentials, distinguishing it from sibling tools like vault_lock (which locks) and vault_store (which requires prior unlock).

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 indicates when to use this tool ('Required before storing or using credentials'), providing clear context for its necessity. It does not explicitly state when not to use or describe alternatives, but the sibling names imply vault_lock is the inverse, and the need before other operations is clear.

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