Lock the vault

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

The description transparently explains that key material is dropped and credentials are cleared even if the flush fails, with failures reported back. However, the annotations set destructiveHint to false, which directly contradicts the described destructive credential-clearing behavior. This is an annotation contradiction, so the score is 1.

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 two punchy sentences with no filler, front-loading the emergency warning and covering purpose, failure behavior, and reporting. Every sentence earns its place.

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 zero-parameter tool with an output schema, the description covers what is flushed, sealed, or dropped, the guarantee that clearing still happens on partial failure, and that failures are reported. An agent has enough detail to invoke and understand the result.

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?

The tool takes zero parameters, so there are no parameter semantics to document. The description's emphasis on the operation's behavior is sufficient for a parameterless tool.

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 uses an imperative 'flush, seal, and drop key material now' and clearly names the target resource (the vault, key material, stored credentials). It is easily distinguishable from sibling tools like memory_store or memory_unlock because it targets an emergency lock/clear operation.

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 'PANIC LOCK' label and 'Always available' phrase convey the intended emergency context and reinforce that this tool works even when other operations fail. It does not explicitly list alternatives or exclusions, but the use case is obvious enough from the wording.

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