set_current_scene_transition_duration

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

No annotations are provided, so the description carries the burden. It discloses a conditional behavior (only applies when the transition is not fixed-duration) and the accepted range, but does not state what happens if the transition is fixed-duration or describe side effects/errors.

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 two concise sentences with the purpose first and an Args block below. There is no padding or redundant restatement of the tool name.

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 and no annotations, the description covers purpose, applicability, units, and range. It only lacks explicit behavior when the transition is fixed-duration, which is a minor gap at this complexity.

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?

The schema only provides the type (integer), with no description (0% coverage). The description fully compensates by specifying units ('milliseconds') and the valid range (50-20000), giving the agent complete parameter semantics.

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') and identifies the exact resource ('duration of the current transition') with a scope caveat ('if it isn't fixed-duration'). This clearly distinguishes it from sibling transition tools like set_current_scene_transition_settings.

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 states when the tool is applicable (non-fixed-duration transitions) and implies when not to use it (fixed-duration ones). It does not explicitly name alternatives, but this is a narrow setter and the condition is clear guidance.

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