Set the duration of the current OBS transition in milliseconds to control how long scene switches take.
Set the duration of the current transition in milliseconds
| Name | Required | Description | Default |
|---|---|---|---|
| duration | Yes | The duration to set in milliseconds |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this requires specific permissions, affects ongoing transitions, has side effects, or what happens on success/failure. For a mutation tool, this leaves critical behavioral traits unspecified.
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 a single, efficient sentence with no wasted words. It front-loads the core action and resource, making it immediately understandable and well-structured for quick comprehension.
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 incomplete. It lacks information on behavioral implications (e.g., whether changes are immediate, reversible, or have constraints), expected outcomes, or error conditions, leaving significant gaps for an agent to use it effectively.
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 100%, with the parameter 'duration' fully documented in the schema. The description adds no additional meaning beyond implying the parameter is for the 'current transition', which is already clear from the tool name and schema context. Baseline 3 is appropriate as the schema does the heavy lifting.
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 states the action ('Set') and target ('duration of the current transition'), specifying the unit ('milliseconds'). It distinguishes from siblings like 'obs-get-transition-duration' by indicating a write operation, though it doesn't explicitly differentiate from other set tools like 'obs-set-transition-settings' beyond the specific property being set.
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 provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active transition), exclusions, or compare with similar tools like 'obs-set-transition-settings' for broader transition modifications.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.