Set Transition Duration

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict these. The description adds the "current transition" scoping, which is useful, but it omits any detail about whether the change takes effect immediately, affects in-progress transitions, or requires a transition to be active. With annotations present, the added behavioral context is minimal.

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 clear sentence with zero filler. It states the action, target, and unit efficiently.

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 one-parameter setter with no output schema, the description covers the essential information: what is set, on what (current transition), and in what unit. It could be improved by noting whether a current transition must already exist, but this is a minor gap given the tool's simplicity and the idempotent annotation.

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 duration parameter already documented as "The duration to set in milliseconds." The description adds no additional parameter semantics beyond the schema, so the baseline of 3 applies.

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 "Set" with a clear resource: "the duration of the current transition." It distinguishes itself from sibling tools like obs-get-transition-duration (get vs set) and obs-set-transition-settings (which handles broader settings). Units are also specified (milliseconds).

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?

The description implies when to use it (when you want to change the current transition's duration) but does not explicitly state prerequisites, such as having a current transition set via obs-set-current-transition, or when to prefer obs-set-transition-settings instead. No explicit alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.