Set transition duration

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Set the duration' without explaining whether the change is temporary, whether it affects future transitions, error conditions, or reversibility. Minimal transparency for a mutation tool.

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, focused sentence with no superfluous information. It is front-loaded with the verb and resource, making it immediately understandable.

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 tool, the description lacks essential context: when to use it, prerequisites (active transition), and behavioral implications. The output schema exists but does not replace the need for usage context or side-effect disclosure. Inadequate for an agent to confidently choose and invoke it without additional investigation.

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 has no description for duration_ms (0% coverage), so the description must compensate. It clarifies the unit (ms) and the scope (active scene transition), but it does not specify allowed values, constraints, or default behavior. Adds some meaning but not comprehensive.

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 the specific resource (duration of the active scene transition), using a precise verb and object. It is distinct from sibling tools like set_scene_transition, which sets the transition type, and trigger_transition, which triggers it. No ambiguity or tautology.

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, prerequisites, or exclusions. For example, it does not mention that an active transition must exist or how this tool relates to set_scene_transition.

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