Replace a single scene's media asset without regenerating the script or other scene choices; use it to swap visuals in an existing storyboard while keeping all other selections intact.
Replace one scene's media choice without regenerating its script or other choices.
| Name | Required | Description | Default |
|---|---|---|---|
| asset_id | Yes | ||
| scene_id | Yes | ||
| storyboard_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral context by explaining the non-side-effect behavior of the mutation (not regenerating scripts or other choices), which is a high-value detail beyond what the annotations or schema convey.
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 definition is a highly efficient single sentence that packs the action, target, and behavioral constraints into one concise statement.
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 this mutation tool, it is extremely complete. It explicitly addresses the scope of change and lack of downstream cascading effects, which is exactly the context an agent needs to invoke it correctly.
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?
With 0% schema description coverage, the description must carry the semantic weight. It establishes that the inputs relate to 'scene' and 'media choice,' providing necessary conceptual meaning for the required IDs.
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 clearly identifies the action ('Replace') and the resource ('scene's media choice'), providing a distinct purpose that differentiates it from sibling tools like search_media or generate_video.
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?
It provides a critical constraint for usage: the replacement is performed 'without regenerating its script or other choices.' This clearly defines the boundaries of the tool's functionality.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.