Reveal a Stillvault secret value (exposes it to the model)

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

Without annotations, the description warns about exposing the secret to model context and provider logs, and explains the human approval blocking behavior. This fully discloses the tool's impact.

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?

Four sentences, each carrying essential information: purpose, warning, alternative, usage context. Front-loaded with key action and important warning.

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 tool with one parameter, no output schema, and no annotations, the description covers all necessary aspects: purpose, usage, warnings, behavioral expectations, and alternative. Complete.

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 single parameter 'path' is well-described in the schema. The description adds practical detail about the prefix format, but schema coverage is 100%, so description adds marginal value.

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 returns a secret's plaintext value after human approval. Distinguishes from sibling stillvault_run by specifying that it exposes the value, whereas stillvault_run uses it without revealing.

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 advises preferring stillvault_run unless the value must be read, provides specific use cases (display to human, write to a file), and notes that the call blocks until human approval.

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