Overwrite an existing Roblox Studio script's source code by providing its path and new Luau source. Use to update or replace script logic during automated scene and script building.
Overwrite Source of an existing script.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| source | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It says it overwrites source of an existing script, implying destruction of prior content, but omits permissions, reversibility, error handling for missing scripts, and side effects.
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?
A single front-loaded sentence with no wasted words. However, its extreme brevity contributes to underspecification rather than efficient completeness.
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 mutation tool with no annotations and no output schema, the description is too sparse. It should cover path format, overwrite behavior, and potential errors to be 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?
Schema description coverage is 0%, so the description must explain the two parameters. It alludes to a 'Source' (source) and an 'existing script' (path), but provides no format, constraints, or examples, leaving both parameters underspecified.
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 'Overwrite' and resource 'Source of an existing script', making the core action clear. It implicitly distinguishes itself from create_script/read_script by targeting an existing script, but does not explicitly name alternatives.
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?
Offers no guidance on when to use this tool versus create_script, read_script, or other script tools. No prerequisites, exclusions, or alternative conditions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.