Writes UTF-8 or base64-decoded content to a writable branch and creates a deduplicated checkpoint, keeping main changes isolated until publish.
Write UTF-8 or base64-decoded binary content on a writable branch, creating a deduplicated checkpoint. main changes only through publish.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| branch | Yes | ||
| content | Yes | ||
| message | No | ||
| encoding | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations, the description usefully discloses that each write produces a deduplicated checkpoint and that main is protected from direct writes. But it does not disclose what a write to an existing path does (overwrite vs. fail), nor what is destroyed despite destructiveHint=true, nor the return value, for a tool with no output schema.
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?
Two dense sentences, no filler, with the core operation stated first and the branch-scope caveat second. Every clause carries information.
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 5-parameter destructive write with no output schema and zero schema documentation, the description is too thin: it omits the 'message' parameter entirely, says nothing about overwrite/error behavior on existing paths, and gives no hint of what the operation returns (e.g., a checkpoint/commit identifier).
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 description coverage is 0%, so the description must carry the burden. It only illuminates 'encoding' (utf8 vs base64) and the writable-branch constraint on 'branch'; the required 'path' (must match ^\/) and especially the 'message' property — which content is oddly $ref'd to — remain completely unexplained.
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?
States a specific verb and resource ('Write UTF-8 or base64-decoded binary content') plus the scope constraint ('on a writable branch') and a side effect ('creating a deduplicated checkpoint'). It also carves out the main-branch case ('main changes only through publish'), which separates it from layerfs_branch_publish, though it does not distinguish itself from layerfs_fs_edit or layerfs_fs_apply.
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?
'On a writable branch' and 'main changes only through publish' give one explicit routing rule toward layerfs_branch_publish for main. However, no guidance is offered on when to use this versus layerfs_fs_edit (in-place edit) or layerfs_fs_apply (multi-file/structured changes), which is the most likely ambiguity an agent faces in this sibling set.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.