editor_open_scene

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call is synchronous ('returns when it has loaded') and that it is refused during play mode. However, it does not explain what happens to any currently open scene or unsaved changes, which is important for an editor-state mutation.

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 three tight sentences with no wasted language. The core purpose is front-loaded, followed by path semantics and the play-mode restriction.

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 one-parameter editor tool with a full input schema and an output schema, the description covers the essential call behavior: what it does, how paths are resolved, and when it is refused. The main missing context is how it handles unsaved state in the currently open scene.

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 coverage is already 100%, so the baseline is 3. The description adds useful meaning by explaining that the path can be absolute or relative to Content/ and by providing an example such as Scenes/Main.scene.

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 and resource: 'Opens a scene in the live Flax Editor.' It also states the synchronous completion behavior ('returns when it has loaded'), making it clearly distinguishable from listing or inspecting siblings such as scene_list and scene_outline.

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 gives clear usage context, including path resolution relative to the project's Content folder and an example path. It also provides an explicit exclusion: 'Refused during play mode.' It does not name an alternative tool, but the when-to-use and when-not-to-use conditions are clear.

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