set_scene_transition_override

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

No annotations are provided, so the description carries the disclosure burden. It explains the effect (override on switching into the scene), the meaning of None to clear, and a valid duration range (50-20000 ms). However, it does not mention error behavior, permissions, or side effects on existing overrides.

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 compact and well-structured: a single sentence explaining the purpose, followed by a focused Args list. Every line adds value, especially the None-to-clear semantics for both optional parameters.

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 setter with three parameters, the description covers purpose, all parameters, and null semantics. It does not specify return values or error handling, but that is secondary for this type of operation. Given the absence of annotations and output schema, the description handles the essentials well.

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 0%, so the description's Args section is essential. It defines each parameter and adds meaning beyond the schema: scene_name identifies the target scene, transition_name can be None to clear the override, and transition_duration_ms has a range and can also be None to clear.

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 'override' and clearly identifies the resource: the transition used when switching INTO a specific scene. It explicitly contrasts with the 'global current transition', which differentiates it from sibling tools like set_current_scene_transition.

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 gives clear context for when to use this tool: to set a per-scene override instead of the global transition. However, it does not explicitly name alternatives or state when not to use it, only implying the contrast with global transition setters.

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