Save data to shared storage for cross-agent access. JSON strings are handled automatically, and restricted protected keys remain unavailable for writes.
Write data to shared storage. Handles JSON strings automatically. Protected keys are restricted.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | ||
| value | Yes |
Changes observed during successful MCP inspections.
v0.3.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden. It adds useful behavior by saying JSON strings are handled automatically and protected keys are restricted, but it does not disclose overwrite behavior, failure behavior, permissions, or what happens when a protected key is used.
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 short sentences with the core action front-loaded. There is no padding, and both sentences earn their 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 simple two-parameter write tool, this covers the core operation, JSON handling, and the protected-key constraint. It is still incomplete for safe invocation because it omits what protected keys are, how to format the value, and what happens on error or overwrite.
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 schema has 0% description coverage and the description must compensate. It implies the value can be a JSON string but does not explain key uniqueness, namespacing, value formatting, length limits, or how protected keys are identified.
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 a specific verb-resource pairing ('Write data to shared storage'), and the action is unmistakable. Mentioning JSON-string handling and protected-key restrictions also helps distinguish it from read_storage and storage_cleanup.
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?
No guidance is given about when to use this tool versus siblings such as read_storage or storage_cleanup. The protected-key note hints at a limitation but is not a practical when-to-use or when-not-to-use instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.