Persist a JSON-serialisable value under a hashed key in the miniCloud Vault. Cost: 0.001 USDC via Skyfire. Redeemed immediately on each call. Requires a valid skyfire-pay-id header.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Unique identifier for the stored value. SHA-256 hashed before storage for privacy. | |
| value | Yes | Any JSON-serialisable value to store. Must not be null or undefined. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the immediate monetary cost (0.001 USDC), the redemption semantics, and the required authentication header. With no annotations provided, this additional behavioral context is valuable, though it does not cover overwrite behavior or return values.
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 efficiently structured with four short sentences, each conveying essential information: purpose, cost, redemption, and auth requirement. No redundant wording is present.
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 two-parameter schema and lack of output schema, the description adequately covers the tool's operational context, including cost and auth. It misses potential overwrite behavior but remains largely complete for a straightforward save operation.
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 input schema already provides 100% coverage of both parameters, including detailed descriptions for key hashing and value constraints. The description adds no additional parameter semantics beyond what the schema states, so the baseline score of 3 applies.
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 the specific verb 'Persist' and identifies the resource as 'value under a hashed key in the miniCloud Vault,' clearly distinguishing it from the sibling tool vault_recall which would retrieve values.
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?
While the description clearly implies this is for storing values, it does not explicitly state when to use this tool versus vault_recall or any exclusions. The usage context is implied by the verb 'Persist' but no explicit guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools are opposites: vault_save persists a value, vault_recall retrieves it. Their purposes are completely distinct with no overlap, so an agent can easily choose the correct one.
Both tools follow the same verb_noun pattern: vault_save and vault_recall. The naming is perfectly consistent, using snake_case throughout.
Two tools is on the thin side for a vault service. While save and recall cover the core, the count feels minimal and might benefit from additional operations like list or delete.
The toolset lacks standard vault management operations such as deleting keys or listing existing keys. This means agents cannot fully manage the vault lifecycle, only save and retrieve.